Hi,
Updated packages will be in the repo in the next hour or so. Apologies
for the inconvenience.
Regards, Devrim
On Wed, 2013-09-18 at 13:56 +, kyri...@alumni.princeton.edu wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8463
> Logged by: Kriton
Hi Keikki,
it is clear what causes this problem, but pg_upgradecluster is an operation
which simply MUST work (if you have several hundred of user databases, it is
not an option to check all of them for this kind of error before the cluster
upgrade).
Database upgrade is performed by the server
Right after a fresh initdb on a 9.3 or master database:
postgres=# select oid,relname,relminmxid from pg_class where
relname='pg_database';
oid | relname | relminmxid
--+-+
1262 | pg_database | 4244967297
(1 row)
That bogus value seems to appear already some
Hello Michael,
Thanks for your answer.
On Thu, Sep 19, 2013 at 4:46 AM, Michael Paquier
wrote:
> On Tue, Sep 17, 2013 at 4:48 PM, Marcelo Bacha wrote:
> > I have an OpenBSD 5.3 server, with PostgreSQL 9.3.0, which seems to work
> > fine. I´m trying to install on it, which always worked fine.
>
On 13.09.2013 15:13, stu...@stuartbishop.net wrote:
pg_basebackup blocks until all necessary WAL files have been archived by
archive_command. This can take a few minutes under normal circumstances, and
indefinitely if archive_command is failing.
I would like to be able to disable this check, as
On 21.09.2013 20:16, jan.m...@inf-it.com wrote:
today I tried to upgrade from 9.2 to 9.3 (pg_upgradecluster 9.2 main) and
the upgrade of one of my databases failed with the following error: "ERROR:
new row for relation ... violates check constraint ...".
I created an example to reproduce this bu
On 16.09.2013 22:59, Andrew Gierth wrote:
"Heikki" == Heikki Linnakangas writes:
Heikki> Attached is a patch to fix both of these issues. I'm too
Heikki> tired right now to thoroughly test it and commit, so I'll get
Heikki> back to this tomorrow. Meanwhile, please take a look and let
