query logging of prepared statements

2019-02-08 Thread Justin Pryzby
A couple months ago, I implemented prepared statements for PyGreSQL. While updating our application in advance of their release with that feature, I noticed that our query logs were several times larger. With non-prepared statements, we logged to CSV: |message| SELECT 1 With SQL

Re: Server goes to Recovery Mode when run a SQL

2019-02-08 Thread PegoraroF10
*Well, now we have two queries which stops completelly our postgres server. That problem occurs on 10.6 and 11.1 versions. On both server the problem is the same. Linux logs of old crash are:* Feb 1 18:39:53 fx-cloudserver kernel: [ 502.405788] show_signal_msg: 5 callbacks suppressedFeb 1 18:39

Re: [EXTERNAL]Re: Server goes to Recovery Mode when run a SQL

2019-02-08 Thread Jeremiah Bauer
You are running afoul of the Linux OOM killer which is what the kernel uses when it experiences memory pressure. You could exclude PostgreSQL from the OOM killer, you'll need to look up on how to do that for your particular Linux distro. We've experienced this with queries that consume more RAM

Re: Server goes to Recovery Mode when run a SQL

2019-02-08 Thread Adrian Klaver
On 2/8/19 1:11 PM, PegoraroF10 wrote: *Well, now we have two queries which stops completelly our postgres server. That problem occurs on 10.6 and 11.1 versions. On both server the problem is the same. * *Linux Log of new crash, which takes several minutes to stop:* Feb 8 15:06:40 fxReplicati