Re: [HACKERS] Safer and faster get_attstatsslot() - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Safer and faster get_attstatsslot()
Date
Msg-id CANP8+jKP0BPz+2Yd1WANev+w7R4T--FfSgWh=DHMMefpQZ61Kg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Safer and faster get_attstatsslot()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Safer and faster get_attstatsslot()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11 May 2017 at 17:41, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> ...because code that worked fine for Peter and me failed
> erratically in the buildfarm.

I think its always a little bit too exciting for me also.

I suggest we have a commit tree and a main tree, with automatic
copying from commit -> main either
1. 24 hours after commit
2. or earlier if we have a full set of green results from people
running the full suite on the commit tree

That way we don't have to polute the main tree with all this jumping around.

Many alternate ideas possible.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] export import bytea from psql
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] WITH clause in CREATE STATISTICS