Patric Bechtel writes:
> My platform: Ubuntu 12.04, PostgreSQL 9.2beta1, tried it with 9.1 with same
> result.
> postgresql.conf is stock, except for timezone, which is set to Asia/Manila.
> $ createdb -U postgres tztest
> $ psql tztest postgres
> tztest=# create table foo (bar int, baz timestam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have the following strange effect, maybe someone has an idea on wether this
is 'normal' or a bug:
My platform: Ubuntu 12.04, PostgreSQL 9.2beta1, tried it with 9.1 with same
result.
postgresql.conf is stock, except for timezone, which is set
Hi,
2 possible bugs in pg_dump/pg_restore related to
large objects.
1. Large objects dumped, deleted then restored
do not retain their original OIDs. Big problem as we reference their OIDs
in tables.
2. The pg_restore command --list indicated no Blobs
in the dump file even when there ar
m Lane" <[EMAIL PROTECTED]>
To: "Colin Stearman" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, November 24, 2002 12:57 PM
Subject: Re: [BUGS] pg_dump/pg_restore
"Colin Stearman" <[EMAIL PROTECTED]> writes:
> 1. Large objects dumped, deleted t
"Colin Stearman" <[EMAIL PROTECTED]> writes:
> 1. Large objects dumped, deleted then restored do not retain their original=
> OIDs. Big problem as we reference their OIDs in tables.
They're not supposed to (indeed cannot). pg_restore is supposed to arrange
for references to large-object OIDs to
Hi,
2 possible bugs in pg_dump/pg_restore related to
large objects.
1. Large objects dumped, deleted then restored
do not retain their original OIDs. Big problem as we reference their OIDs
in tables.
2. The pg_restore command --list indicated no Blobs
in the dump file even when there a
