| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Separate block sampling functions |
| Date: | 2015-05-18 22:36:16 |
| Message-ID: | 23094.1431988576@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
I wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> What is the current state of this? Are we sticking with what Tom
>> classified as drive-by breakage?
> Since I was the one complaining, I'm willing to do the legwork to
> insert a compatibility shim. I probably won't get to it today though,
> this being release wrap day. In the meantime please leave
> FileTextArrayFDW as-is.
I put in a shim --- crake should be happy again on its next run.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-18 23:58:47 | pgsql: Attach ON CONFLICT SET ... WHERE to the correct planstate. |
| Previous Message | Tom Lane | 2015-05-18 22:34:55 | pgsql: Put back a backwards-compatible version of sampling support func |