| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bosco Rama <postgres(at)boscorama(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Large object corruption during 'piped' pg_restore |
| Date: | 2011-01-20 21:41:45 |
| Message-ID: | 21625.1295559705@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Bosco Rama <postgres(at)boscorama(dot)com> writes:
> We've discovered (or possibly rediscovered?) a corruption when restoring large
> objects.
> If 'standard_conforming_strings = on' is set in our DB (which is required for
> our app) then the piped restore method (e.g. pg_restore -O backup.dat | psql)
> results in the large objects being corrupted.
This vaguely reminds me of some long-since-fixed bug, but since you have
neglected to give any version details, it's hard to say for sure.
What PG version was the original server? The pg_dump you used to make
the backup? The pg_restore? The target server?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bosco Rama | 2011-01-20 22:07:01 | Re: Large object corruption during 'piped' pg_restore |
| Previous Message | Bosco Rama | 2011-01-20 21:24:35 | Large object corruption during 'piped' pg_restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-01-20 21:42:45 | Re: estimating # of distinct values |
| Previous Message | Simone Aiken | 2011-01-20 21:40:09 | Re: ToDo List Item - System Table Index Clustering |