Adrian Klaver writes:
> On 04/18/2018 07:22 AM, Tom Lane wrote:
>
>> Pavel Raiskup writes:
>>> . and it seems like the hstore.so was somewhat intimately integrated into
>>> OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
>>> --format=custom' called through 'pg_upgrade' fail
On 04/18/2018 08:04 AM, Pavel Raiskup wrote:
On Wednesday, April 18, 2018 4:43:01 PM CEST Adrian Klaver wrote:
I am obviously missing something. If the old server was using hstore in
a database how could hstore.so could be accessible to it but not pg_dump?
Because on Fedora we usually run pg
On Wednesday, April 18, 2018 4:43:01 PM CEST Adrian Klaver wrote:
> On 04/18/2018 07:22 AM, Tom Lane wrote:
> > Pavel Raiskup writes:
> >> . and it seems like the hstore.so was somewhat intimately integrated into
> >> OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
> >> --for
On Wednesday, April 18, 2018 4:22:23 PM CEST Tom Lane wrote:
> Pavel Raiskup writes:
> > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1557490
>
> There are certainly plenty of reasons why extension .so's might be needed
> during pg_dump, even in a binary-upgrade situation. The first example
>
On 04/18/2018 07:22 AM, Tom Lane wrote:
Pavel Raiskup writes:
. and it seems like the hstore.so was somewhat intimately integrated into
OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
--format=custom' called through 'pg_upgrade' failed with:
pg_dump: [archiver (db)] que
Pavel Raiskup writes:
> . and it seems like the hstore.so was somewhat intimately integrated into
> OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
> --format=custom' called through 'pg_upgrade' failed with:
> pg_dump: [archiver (db)] query failed: ERROR: could not access
On 04/18/2018 07:07 AM, Pavel Raiskup wrote:
Hi all,
with a huge delay, I've seen this question [1].
. and it seems like the hstore.so was somewhat intimately integrated into
OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
--format=custom' called through 'pg_upgrade' faile
Hi all,
with a huge delay, I've seen this question [1].
. and it seems like the hstore.so was somewhat intimately integrated into
OP's database so the '/usr/bin/pg_dump --schema-only --binary-upgrade
--format=custom' called through 'pg_upgrade' failed with:
pg_dump: [archiver (db)] query faile
