Re: [COMMITTERS] pgsql: Stamp 9.2.24.

2017-11-06 Thread Vik Fearing
On 11/06/2017 11:23 PM, Peter Geoghegan wrote: > Tom Lane wrote: >> Stamp 9.2.24. > > Uh, I thought 9.2 was EOL. Actual EOL is always the next minor version after the expiration date. Otherwise, it'd be the version before the expiration date which is naturally too s

Re: [COMMITTERS] pgsql: Add pg_size_bytes() to parse human-readable size strings.

2016-02-20 Thread Vik Fearing
On 02/20/2016 11:17 AM, Dean Rasheed wrote: > On 20 February 2016 at 10:12, Michael Paquier > wrote: >> Happy first commit. > > Arg. Not so much. > > Looks like I broke something -- looking into it now :-( Happy first commit anyway! -- Vik Fearing

Re: [COMMITTERS] pgsql: Update pg_stat_statements extension for parallel query.

2016-06-16 Thread Vik Fearing
ode will look really weird because it'll be missing a version. Attached is my attempt to fix this. It might not be the best way to do it, but I feel that *something* should be done. -- Vik Fearing +33 6 46 75 15 36 http://2ndQuadrant.fr Post

Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in

2017-03-16 Thread Vik Fearing
On Thu, Mar 16, 2017 at 11:39 PM, Andrew Gierth wrote: > Avoid having vacuum set reltuples to 0 on non-empty relations in the > presence of page pins, which leads to serious estimation errors in the > planner. This particularly affects small heavily-accessed tables, > especially where locking (e