--On 9. Juli 2013 22:05:20 + lal...@fhcrc.org wrote:
I have found that if you change the password in the USER MAPPING, that
postgres_fdw will not use it unless the current password fails or you
close and re-open your postgres connection. I found this while testing to
see if the USER MAPPIN
--On 21. September 2012 10:25:50 +0200 Andres Freund
wrote:
We had a similar issue at a customer site. The server was shut down for
updating it from 9.1.4 to 9.1.5, after starting it again the log was
immediately cluttered with
How was it shutdown? -m fast or -m immediate?
-m fast
ERR
--On 20. September 2012 18:18:12 -0400 Tom Lane wrote:
If it were an actual TRUNCATE, yeah. But it could be a case of VACUUM
truncating a now-empty table to zero blocks.
But nothing like this would explain the OP's report that corruption is
completely reproducible for him. So I like your t
--On 23. März 2011 20:37:11 + Simon Riggs wrote:
The patches are slightly different because the infrastructure isn't
all there in 8.4.
Please can you test these before I commit to 8.4.
Hi Simon,
I've searched the committers mailinglist wether this is already committed, but
either i'v
--On 12. Juli 2011 04:32:11 + David Carlos Manuelda
wrote:
The following bug has been logged online:
Bug reference: 6113
Logged by: David Carlos Manuelda
Email address: stormb...@gmail.com
PostgreSQL version: 9.0.4
Operating system: Gentoo Linux
Description:
--On 17. Juni 2011 08:18:03 + Christoph Berg wrote:
In German locale, the follow statement causes vsnprintf() to segfault when
printing the hint:
SELECT TO_DATE('30.12.2011', 'MMDD') AS datum;
Fix tested for 8.4:
Additionally, this seems to be the case for 9.0, 9.1 and current -HE
--On 12. Mai 2011 11:24:13 -0400 Tom Lane wrote:
This is on the
to-fix list --- in fact there was a patch submitted for it last year,
although it got returned for rework and we've not seen it again yet.
Yes, I didn't manage to provide a completed patch for 9.1...will try to
re-submit for 9
--On 23. März 2011 20:37:11 + Simon Riggs wrote:
The patches are slightly different because the infrastructure isn't
all there in 8.4.
Please can you test these before I commit to 8.4.
FYI, we have deployed patched RPMs to one of the standby servers, the one where
most of the hangs oc
PostgreSQL is 8.4.7, WAL-Logshipping is actually using SkyTools 2.1.12
(both installed from PGDG rpms), running with CentOS 5.5 XEN-VM with Kernel
2.6.18-194.26.1.el5xen.
recovery.conf on the standby installed by walmgr is
restore_command = '/usr/bin/walmgr.py
/media/pgarchive/wal-config/wal-
--On 20. Januar 2011 21:56:44 + Thom Brown wrote:
Known bug in OSX's libedit. Use readline instead.
http://archives.postgresql.org/pgsql-bugs/2010-04/msg00127.php
regards, tom lane
How do I force readline? I'm not using --with-libedit-preferred or
--without-re
--On 12. Juli 2010 14:39:19 -0400 Tom Lane wrote:
Yeah. Past discussions of this have leaned to the viewpoint that we
should disallow the above, ie it should not be possible to have NOT NULL
on the parent unless all the children have it too. Nobody's got round
to implementing it though. Th
--On 4. Juni 2010 15:19:42 -0400 Bruce Momjian wrote:
That would make the bug go away,
rather than require users to use a special flag (and find out only after
they were doing the reload).
Out of curiosity, why is this a "bug" now? We recommend migration
procedures always to use the pg_dum
--On Donnerstag, Dezember 21, 2006 15:47:40 + Tony Marston
<[EMAIL PROTECTED]> wrote:
The fact that the SQL standard says that the schemata view is supposed to
"Identify the schemata in a catalog that are owned by a given user" does
not automatically mean that the information can *ONLY* be
13 matches
Mail list logo
