could not open file "@1@" for reading: @2@
could not read file "@1@": @2@
could not read file "@1@": read @2@ of @3@
incorrect checksum in userlog_control file
userlog_control was initialized by PostgreSQL version @1@, which is not compatible with this version @2@
startup failed because userlog.directory is not set
userlog directory "@1@" is too long
startup failed because userlog.archive_directory is not set
archive directory "@1@" is too long
could not access directory "@1@": @2@
userlog.directory and userlog.archive_directory must be different
could not open directory "@1@": @2@
invalid list syntax in parameter "@1@"
userlog extension can use only "logical" for wal_level
userlog extension requires for archive_mode to be "on" or "always"
no userlog is extracted if starting the PostgreSQL server as a standby and archive_mode is not "always"
no userlog is extracted because archive_command is not set
@1@ (PID @2@) exited with exit code @3@
terminating postmaster process due to userlog daemon
could not start as primary server because the userlog_control file was created with the follow-primary option
failed to update userlog_control
out of memory
new extraction target timeline is @1@
could not write extracted file
archive file may be corrupted
could not seek in log file @1@ to offset @2@: @3@
could not fsync file "@1@": @2@
could not close file "@1@": @2@
could not create file "@1@": @2@
could not prepare SQL statement "@1@"
failed to get flush_lsn of downstream standby server
could not write file "@1@": @2@
pgx_emit_userlog() cannot be called in a subtransction
sum of userlog exceeds userlog.limit_size_per_xact
set-valued function called in context that cannot accept a set
materialize mode required, but it is not allowed in this context
return type must be a row type
could not open lock file "@1@" for reading: @2@
could not read lock file "@1@": @2@
lock file "@1@" is empty
bogus data in lock file "@1@": "@2@"
command cannot be executed because there is the PostgreSQL server process (PID @1@) running in the data directory "@2@"
out of memory
could not open file "@1@" for writing: @2@
could not write file "@1@": @2@
clusters are not compatible with this version of pgx_userlog_control
could not create file "@1@": @2@
could not fsync file "@1@": @2@
could not close file "@1@": @2@
could not rename file "@1@": @2@
could not open file "@1@" for reading: @2@
invalid WAL segment size
argument of --wal-segsize must be a number
could not read file "@1@": @2@
could not read file "@1@": read @2@ of @3@
incorrect checksum in file "@1@"
userlog_control is not compatible with this version of pgx_userlog_control
could not parse start WAL location "@1@"
userlog directory "@1@" is too long
too many command-line arguments (first is "@1@")
unrecognized operation mode "@1@"
no operation specified
at least one -l option or --follow-primary option must be specified
cannot specify both -l option and --follow-primary option
-l option can be used only in set operation mode
--follow-primary option can be used only in set operation mode
--wal-segsize option can be used only in show operation mode
no userlog directory specified
no database directory specified and environment variable PGDATA unset
calculated CRC checksum does not match value stored in pg_control
user name lookup failure: error code @1@
could not look up local user ID @1@: @2@
local user with ID @1@ does not exist
メッセージ集の先頭へ
