Like your customer, this bug has blown up my standby servers, twice in the
last month: the first time all 4 replicas, the second time (mysteriously
but luckily) only 1 of them.
At any rate, since the fix isn't available yet, is/are there any
configuration changes that can be made or maintenance pr
I'm not sure it's fixed. I am attempting a pg_upgrade from 9.2.8 to 9.3.5
and it dies like so:
(...many relations restoring successfully snipped...)
pg_restore: creating SEQUENCE address_address_id_seq
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from
usion. If anyone else is
experiencing this bug, they may erroneously be led to believe that 9.3.5
contains the fix.
I will attempt to build 9.3 stable head and retry my upgrade.
On Wed, Sep 3, 2014 at 6:03 PM, Bruce Momjian wrote:
> On Wed, Sep 3, 2014 at 05:12:30PM -0600, Noah Yetter wrote
Thu, Sep 4, 2014 at 11:37:27AM -0600, Noah Yetter wrote:
> > The 9.3.5 release notes contain...
> >
> >
> > • Fix pg_upgrade for cases where the new server creates a TOAST table
> but the
> > old version did not (Bruce Momjian)
> >
> > This ra
Doing the upgrade with an installation built from REL9_3_STABLE at
commit 52eed3d4267faf671dae0450d99982cb9ba1ac52 was successful.
The view that I saw get re-created as a table doesn't have any circular
references, or indeed any references to other views, nor do any other views
reference it. But
offered by
dblink() makes it preferable to fixed foreign tables.
S... what gives? This seems like a really obvious security hole. I've
searched the mailing list archives repeatedly and found zero discussion of
this issue.
--
Noah Yetter
Data Architect/DBA @ Craftsy
