|
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* syslogger.h
|
|
|
|
|
* Exports from postmaster/syslogger.c.
|
|
|
|
|
*
|
|
|
|
|
* Copyright (c) 2004-2024, PostgreSQL Global Development Group
|
|
|
|
|
*
|
|
|
|
|
* src/include/postmaster/syslogger.h
|
|
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
#ifndef _SYSLOGGER_H
|
|
|
|
|
#define _SYSLOGGER_H
|
|
|
|
|
|
|
|
|
|
#include <limits.h> /* for PIPE_BUF */
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Primitive protocol structure for writing to syslogger pipe(s). The idea
|
|
|
|
|
* here is to divide long messages into chunks that are not more than
|
|
|
|
|
* PIPE_BUF bytes long, which according to POSIX spec must be written into
|
|
|
|
|
* the pipe atomically. The pipe reader then uses the protocol headers to
|
|
|
|
|
* reassemble the parts of a message into a single string. The reader can
|
|
|
|
|
* also cope with non-protocol data coming down the pipe, though we cannot
|
|
|
|
|
* guarantee long strings won't get split apart.
|
|
|
|
|
*
|
|
|
|
|
* We use non-nul bytes in is_last to make the protocol a tiny bit
|
|
|
|
|
* more robust against finding a false double nul byte prologue. But
|
|
|
|
|
* we still might find it in the len and/or pid bytes unless we're careful.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifdef PIPE_BUF
|
|
|
|
|
/* Are there any systems with PIPE_BUF > 64K? Unlikely, but ... */
|
|
|
|
|
#if PIPE_BUF > 65536
|
|
|
|
|
#define PIPE_CHUNK_SIZE 65536
|
|
|
|
|
#else
|
|
|
|
|
#define PIPE_CHUNK_SIZE ((int) PIPE_BUF)
|
|
|
|
|
#endif
|
|
|
|
|
#else /* not defined */
|
|
|
|
|
/* POSIX says the value of PIPE_BUF must be at least 512, so use that */
|
|
|
|
|
#define PIPE_CHUNK_SIZE 512
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
typedef struct
|
|
|
|
|
{
|
|
|
|
|
char nuls[2]; /* always \0\0 */
|
|
|
|
|
uint16 len; /* size of this chunk (counts data only) */
|
|
|
|
|
int32 pid; /* writer's pid */
|
|
|
|
|
bits8 flags; /* bitmask of PIPE_PROTO_* */
|
|
|
|
|
char data[FLEXIBLE_ARRAY_MEMBER]; /* data payload starts here */
|
|
|
|
|
} PipeProtoHeader;
|
|
|
|
|
|
|
|
|
|
typedef union
|
|
|
|
|
{
|
|
|
|
|
PipeProtoHeader proto;
|
|
|
|
|
char filler[PIPE_CHUNK_SIZE];
|
|
|
|
|
} PipeProtoChunk;
|
|
|
|
|
|
|
|
|
|
#define PIPE_HEADER_SIZE offsetof(PipeProtoHeader, data)
|
|
|
|
|
#define PIPE_MAX_PAYLOAD ((int) (PIPE_CHUNK_SIZE - PIPE_HEADER_SIZE))
|
|
|
|
|
|
|
|
|
|
/* flag bits for PipeProtoHeader->flags */
|
|
|
|
|
#define PIPE_PROTO_IS_LAST 0x01 /* last chunk of message? */
|
|
|
|
|
/* log destinations */
|
|
|
|
|
#define PIPE_PROTO_DEST_STDERR 0x10
|
|
|
|
|
#define PIPE_PROTO_DEST_CSVLOG 0x20
|
Introduce log_destination=jsonlog
"jsonlog" is a new value that can be added to log_destination to provide
logs in the JSON format, with its output written to a file, making it
the third type of destination of this kind, after "stderr" and
"csvlog". The format is convenient to feed logs to other applications.
There is also a plugin external to core that provided this feature using
the hook in elog.c, but this had to overwrite the output of "stderr" to
work, so being able to do both at the same time was not possible. The
files generated by this log format are suffixed with ".json", and use
the same rotation policies as the other two formats depending on the
backend configuration.
This takes advantage of the refactoring work done previously in ac7c807,
bed6ed3, 8b76f89 and 2d77d83 for the backend parts, and 72b76f7 for the
TAP tests, making the addition of any new file-based format rather
straight-forward.
The documentation is updated to list all the keys and the values that
can exist in this new format. pg_current_logfile() also required a
refresh for the new option.
Author: Sehrope Sarkuni, Michael Paquier
Reviewed-by: Nathan Bossart, Justin Pryzby
Discussion: https://postgr.es/m/CAH7T-aqswBM6JWe4pDehi1uOiufqe06DJWaU5=X7dDLyqUExHg@mail.gmail.com
4 years ago
|
|
|
#define PIPE_PROTO_DEST_JSONLOG 0x40
|
|
|
|
|
|
|
|
|
|
/* GUC options */
|
|
|
|
|
extern PGDLLIMPORT bool Logging_collector;
|
|
|
|
|
extern PGDLLIMPORT int Log_RotationAge;
|
|
|
|
|
extern PGDLLIMPORT int Log_RotationSize;
|
|
|
|
|
extern PGDLLIMPORT char *Log_directory;
|
|
|
|
|
extern PGDLLIMPORT char *Log_filename;
|
|
|
|
|
extern PGDLLIMPORT bool Log_truncate_on_rotation;
|
|
|
|
|
extern PGDLLIMPORT int Log_file_mode;
|
|
|
|
|
|
|
|
|
|
#ifndef WIN32
|
|
|
|
|
extern PGDLLIMPORT int syslogPipe[2];
|
|
|
|
|
#else
|
|
|
|
|
extern PGDLLIMPORT HANDLE syslogPipe[2];
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
extern int SysLogger_Start(void);
|
|
|
|
|
|
|
|
|
|
extern void write_syslogger_file(const char *buffer, int count, int destination);
|
|
|
|
|
|
|
|
|
|
extern void SysLoggerMain(char *startup_data, size_t startup_data_len) pg_attribute_noreturn();
|
|
|
|
|
|
|
|
|
|
extern bool CheckLogrotateSignal(void);
|
|
|
|
|
extern void RemoveLogrotateSignalFiles(void);
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Name of files saving meta-data information about the log
|
|
|
|
|
* files currently in use by the syslogger
|
|
|
|
|
*/
|
|
|
|
|
#define LOG_METAINFO_DATAFILE "current_logfiles"
|
|
|
|
|
#define LOG_METAINFO_DATAFILE_TMP LOG_METAINFO_DATAFILE ".tmp"
|
|
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
8 years ago
|
|
|
#endif /* _SYSLOGGER_H */
|
