Tom Lane wrote:
>
> So I'm not sure whether to fix it, or leave it as a known failure case
> in old branches. Comments?
I understand the reluctance to fool with stable code. I have zero insight
into your installed versions distribution and backward compatibility needs
so any comment I may have
On Thu, Jan 20, 2011 at 6:14 PM, Tom Lane wrote:
> So I'm not sure whether to fix it, or leave it as a known failure case
> in old branches. Comments?
Since there is a workaround, I think it is best to document it and
leave it as-is.
--
Sent via pgsql-general mailing list (pgsql-general@postgr
Bosco Rama writes:
>>> 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.
> All servers and client tools involved are PG 8.4.6 o
Hi Tom,
Tom Lane wrote:
> Bosco Rama 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.d
Bosco Rama 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 obj
