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

From Tom Lane
Subject Re: [HACKERS] Safer and faster get_attstatsslot()
Date
Msg-id 18069.1494523257@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Safer and faster get_attstatsslot()  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> 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

Meh.  We don't really need that in normal development, and for security
patches there's still a problem: we don't want to wait around 24 hours
after the code is public.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] WITH clause in CREATE STATISTICS
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] WITH clause in CREATE STATISTICS