Hi,
On Sat, 2019-02-09 at 15:46 -0600, Justin Pryzby wrote:
> Hi,
>
>
>
> "segfault" seems to mean you hit a bug, which we'll want more
> information to
> diagnose. Could you install debugging symbols ? Ubuntu calls their
> package
> postgresql-10-dbg or similar. And start server with coredu
On Fri, Feb 08, 2019 at 07:29:53AM -0600, Justin Pryzby wrote:
> 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.
Previously sent to -gene
Hi,
On Fri, Feb 08, 2019 at 02:11:33PM -0700, 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 logs of old crash are:*
> Feb 1 18:39:53 fx-cloudserv
Alexander:
On Sat, Feb 9, 2019 at 1:32 PM Alexander Reichstadt wrote:
> I setup trigger functions for logging, and while they do work and get
> triggered, the current_user always insert “postgres” even when
> updates/deletes/inserts are caused by users of another name.
> How do I get it to use
Hi,
I setup trigger functions for logging, and while they do work and get
triggered, the current_user always insert “postgres” even when
updates/deletes/inserts are caused by users of another name.
How do I get it to use the name that caused the update? It seems current_user
is the trigger’s u
On Monday, 4 February 2019 09:14:14 EET Vijaykumar Jain wrote:
> Hi,
Hi,
> with pg v10.1
> we use writes directly to shards, and reads via FDW from all shards (RO)
> our DB size is ~ 500GB each shard, and tables are huge too.
> 1 table ~ 200GB, 1 ~55GB, 1 ~40GB and a lot of small tables, but lar
