On 26/05/2015 10:23, Tatsuo Ishii wrote:
It was fixed in 9.3.7.
OK.
Do you know what the bug number was or what it was called (I've tried
searching for it before posting, but found nothing which seemed to be
the same problem as ours).
Do you know whether, if we upgrade to 9.3.7/8, it will fix the problem
in the current database, or is the data damage 'permanent', so we'll
need to restore from backup and somehow merge in the latest data?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
