On May18, 2012, at 23:18 , Alvaro Herrera wrote:
> Excerpts from Florian Pflug's message of jue may 17 09:08:26 -0400 2012:
>> On May16, 2012, at 15:51 , Tom Lane wrote:
>
>>> It is by design, in that the only contemplated case was truncated-away
>>> pages. I'm pretty hesitant to consider allowin
On Sat, May 12, 2012 at 5:37 AM, Simon Riggs wrote:
> Do we have a full list of externally defined open standards that we follow?
>
> Are there any known incompatibilities from externally defined open standards?
> (I know about the SQL standard stuff).
The documentation is misleading to the point
On Sun, May 13, 2012 at 3:03 PM, Peter Geoghegan wrote:
> On 13 May 2012 18:07, Jeff Janes wrote:
>> I think that pgbench should it make it easy to assess the impact of
>> foreign key constraints.
>
> I agree in principle. I favour being more inclusive about pgbench
> options, even if the need f
I found this in contrib/sepgsql/expected/label.out:
SECURITY LABEL ON COLUMN t2
IS 'system_u:object_r:sepgsql_ro_table_t:s0'; -- be failed
ERROR: improper relation name (too many dotted names):
Contrast with:
SECURITY LABEL ON COLUMN t2.b
IS 'system_u:object_r:sepgsql_ro_table_t:s0';
Currently, psql --version prints something like
psql (PostgreSQL) 9.2beta1
contains support for command-line editing
I think the notice about readline is a leftover from the old days when
psql was often built without any readline support. Nowadays, this looks
like an anomaly, and it doesn't actu
