Hallo again,
I have the situation again, one of 3 slaves was slow to play all the WAL
files and being about 10GB late it crashed with the same error again.
I collected DEBUG4 output in this time:
https://docs.google.com/open?id=0B2NMMrfiBQcLZjNDbU0xQ3lvWms
I hope it will be helpful,
Regards,
-
>
> This email thread from 2010 has a similar problem:
>http://archives.postgresql.org/pgsql-hackers/2010-10/msg00772.php
> What is limiting a fix for this is the breaking of existing behavior,
> and the breaking of indexes used during pg_upgrade.
> I have added your email to the existing T
Hi,
On Thursday, June 07, 2012 12:44:08 PM Valentine Gogichashvili wrote:
> I have the situation again, one of 3 slaves was slow to play all the WAL
> files and being about 10GB late it crashed with the same error again.
>
> I collected DEBUG4 output in this time:
> https://docs.google.com/open?i
Hi,
I seem to have found a bug in Postgres 9.1.3. Apparently timestamp
values are stored correctly in the database, but querying it returns
invalid results. My environment is Windows 7 64bit. The unexpected
result is that timestamps before 1st of May 1921 are displayed
incorrectly when time z
=?ISO-8859-1?Q?Kasper_R=F6nning?= writes:
> I seem to have found a bug in Postgres 9.1.3. Apparently timestamp
> values are stored correctly in the database, but querying it returns
> invalid results. My environment is Windows 7 64bit. The unexpected
> result is that timestamps before 1st of Ma
On Thursday, June 07, 2012 03:58:24 PM Andres Freund wrote:
> Hi,
>
> On Thursday, June 07, 2012 12:44:08 PM Valentine Gogichashvili wrote:
> > I have the situation again, one of 3 slaves was slow to play all the WAL
> > files and being about 10GB late it crashed with the same error again.
> >
>
=?ISO-8859-1?Q?Kasper_R=F6nning?= writes:
> Thank you for the quick reply! I was completely unaware of the old time
> zones of Helsinki! However I'm afraid that the behaviour of Postgresql
> seems plain wrong to me. An example:
> SET TIME ZONE 'Europe/Helsinki';
> DROP TABLE IF EXISTS test1;
>
Hi,
Thank you for the quick reply! I was completely unaware of the old time
zones of Helsinki! However I'm afraid that the behaviour of Postgresql
seems plain wrong to me. An example:
SET TIME ZONE 'Europe/Helsinki';
DROP TABLE IF EXISTS test1;
CREATE TABLE test1 (ts TIMESTAMPTZ);
INSERT INTO
