Re: [HACKERS] BUG: pg_stat_statements query normalization issues with combined queries

Yes. I'll try to put together a patch and submit it to the next CF. Here it is. I'll add this to the next CF. Oops... better without a stupid overflow. Shame on me! -- Fabien.diff --git a/contrib/pg_stat_statements/expected/pg_stat_statements.out

Re: [HACKERS] Cluster wide option to control symbol case folding

On Saturday, December 24, 2016 10:49 PM Tom Lane [mailto:t...@sss.pgh.pa.us] wrote: > No. This has been looked into repeatedly in the past, and we simply don't want to deal with it. Fair enough. We will not pursue the issue then. That is why I asked. Ian Lewis (www.mstarlabs.com) -- Sent

Re: [HACKERS] Cluster wide option to control symbol case folding

On December 24, 2016 9:52 PM Craig Ringer [mailto:craig.rin...@2ndquadrant.com] wrote: > Personally I can see such an option being ok as an initdb-time setting or at CREATE DATABASE time. Case folding can know the current db from global context. > > It'd have to be fast though. Very fast. That

Re: [HACKERS] Cluster wide option to control symbol case folding

"Lewis, Ian \(Microstar Laboratories\)" writes: > Is there any chance that the PostgreSQL developers would accept a new > cluster wide configuration option to control how the system handles > symbol case folding? No. This has been looked into repeatedly in the past, and

Re: [HACKERS] Cluster wide option to control symbol case folding

On 25 Dec. 2016 10:30 am, "Lewis, Ian (Microstar Laboratories)" < ile...@mstarlabs.com> wrote: Is there any chance that the PostgreSQL developers would accept a new cluster wide configuration option to control how the system handles symbol case folding? Probably not as a GUC (configuration

[HACKERS] Cluster wide option to control symbol case folding

Is there any chance that the PostgreSQL developers would accept a new cluster wide configuration option to control how the system handles symbol case folding? Currently PostgreSQL folds all un-quoted symbols to lower case. We would like to add a global configuration option with a name like

Re: [HACKERS] pg_stat_activity.waiting_start

> This is not an easy problem. See our most recent discussion at > https://www.postgresql.org/message-id/flat/31856.1400021891%40sss.pgh.pa.us Thanks for the small test program. I tested it on my MacBook Pro and gettimeofday() was way faster than time(). The clock_gettime() used by the patch

Re: [HACKERS] pg_stat_activity.waiting_start

Joel Jacobson writes: > On Sat, Dec 24, 2016 at 9:00 AM, Tom Lane wrote: >> The difficulty with that is it'd require a gettimeofday() call for >> every wait start. > I don't think we need the microsecond resolution provided by > gettimeofday() via

Re: [HACKERS] Parallel Index-only scan

Extremely sorry for the inconvenience caused, please find the attached file for the latest version of the patch. On Sat, Dec 24, 2016 at 1:41 AM, Robert Haas wrote: > On Fri, Dec 23, 2016 at 3:03 PM, Tom Lane wrote: > > Or in words of one syllable:

Re: [HACKERS] proposal: session server side variables

2016-12-24 12:19 GMT+01:00 Fabien COELHO : > > Hello Pavel, > > Hmmm. Switching role within a transaction. I never did need that... but >>> that is a use case. >>> >> >> Any application with security definer functions - depends on different >> communities - it is used

Re: [HACKERS] proposal: session server side variables

Hello Pavel, Hmmm. Switching role within a transaction. I never did need that... but that is a use case. Any application with security definer functions - depends on different communities - it is used sometimes strongly. Hmmm. So I understand that you would like to do something like: -

Re: [HACKERS] Compiler warning

On Dec 24, 2016 01:21, "Bruce Momjian" wrote: I am seeing this compiler warning in the 9.4 branch: 9.4: basebackup.c:1284:6: warning: variable 'wait_result' set but not used [-Wunused-but-set-variable] This is on Debian Jessie with gcc version 4.9.2. It is from this