Re: pgsql: Separate block sampling functions

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 14:53:51
Message-ID: 14084.1431960831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-05-18 15:04:33 Re: pgsql: Recursively fsync() the data directory after a crash.
Previous Message Andrew Dunstan 2015-05-18 14:45:26 Re: pgsql: Separate block sampling functions