pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedsysout error log being truncated
2+ messages / 2 participants
[nested] [flat]
* sysout error log being truncated
@ 2019-03-08 22:22 Mark Steben <mark.steben@drivedominion.com>
0 siblings, 1 reply; 2+ messages in thread
From: Mark Steben @ 2019-03-08 22:22 UTC (permalink / raw)
To: pgsql-admin
Good afternoon/evening
We run postgres 9.4. We are moving to a new datacenter and are doing the
requisite parallel performance testing.
One of our transactions is a queue processor that generates a ton of insert
statements per run of this transaction - as many as 1000 per run.
What has happened in new datacenter is that these transactions - while
running correctly and completely - do not write all the insert statements
to our sysout log - only some. Here are some of the postgres
configurations for your reference:
syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
# This is only relevant when logging to eventlog (win32):
#event_source = 'PostgreSQL'
# - When to Log -
#client_min_messages = notice
log_min_messages = info
log_min_error_statement = info
log_min_duration_statement = 4000
# - What to Log -
#debug_print_parse = off
#debug_print_rewritten = off
#debug_print_plan = off
#debug_pretty_print = on
#log_checkpoints = off
#log_connections = off
#log_disconnections = off
#log_duration = off
#log_error_verbosity = default
#log_hostname = off
log_line_prefix = '%u@%h:%d '
#log_lock_waits = off
log_statement = 'ddl'
#log_temp_files = -1
log_timezone = 'US/Eastern'
The only other difference I can report is the minor version
CURRENT PRODUCTION: 9.4.8
NEW DATACENTER: 9.4.21
Any insights welcome - thank you,
--
*Mark Steben*
Database Administrator
@utoRevenue <http://www.autorevenue.com/; | Autobase
<http://www.autobase.net/;
CRM division of Dominion Dealer Solutions
95D Ashley Ave.
West Springfield, MA 01089
t: 413.327-3045
f: 413.383-9567
www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com <http://www.autorevenue.com/;
<http://autobasedigital.net/marketing/DD12_sig.jpg;
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: sysout error log being truncated
@ 2019-03-08 23:09 Tom Lane <tgl@sss.pgh.pa.us>
parent: Mark Steben <mark.steben@drivedominion.com>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2019-03-08 23:09 UTC (permalink / raw)
To: Mark Steben <mark.steben@drivedominion.com>; +Cc: pgsql-admin
Mark Steben <mark.steben@drivedominion.com> writes:
> One of our transactions is a queue processor that generates a ton of insert
> statements per run of this transaction - as many as 1000 per run.
> What has happened in new datacenter is that these transactions - while
> running correctly and completely - do not write all the insert statements
> to our sysout log - only some.
Most, if not all, implementations of syslog will drop messages under
sufficient load; I think they consider that a feature. It's not Postgres'
fault and there's nothing we can do about it. Use a different logging
mechanism if you can't afford to lose any messages.
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2019-03-08 23:09 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-03-08 22:22 sysout error log being truncated Mark Steben <mark.steben@drivedominion.com>
2019-03-08 23:09 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox