Adrian Klaver schrieb am 28.05.2017 um 17:51:
After I finally found the EnterpriseDB Beta binaries (they are pretty well
hidden) I tested with those, and everything works fine there.
For those following along, where would that be?
Here they are:
https://www.enterprisedb.com/products-service
Thomas Kellerer writes:
> Tom Lane schrieb am 26.05.2017 um 20:18:
>>> The error message reported in the logfile is:
>>> pg_dump: unrecognized collation provider: p
>> Ugh :-( ... seems like a rather obvious typo in dumpCollation().
>> Thanks for finding it!
> When I drop that collation from the
On 05/28/2017 08:41 AM, Thomas Kellerer wrote:
Tom Lane schrieb am 26.05.2017 um 20:18:
Apparently BigSQL forgot to include contrib/xml2 in their distribution;
you should ping them about that one.
I can confirm that it's a BigSQL problem.
After I finally found the EnterpriseDB Beta binaries
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/po
Thomas Kellerer writes:
> Interesting enough, the same error message appears when I run "create
> extension xml2;" on Postgres 10.
Sure, that no doubt is exactly the command getting issued during the
pg_upgrade attempt.
> It somehow looks as if there is a DLL dependency between XML2 and whateve
Adrian Klaver schrieb am 26.05.2017 um 23:41:
If that's coming from port/dynloader/win32.c, as I think it must be
because the non-conformant-to-message-style-guidelines phrase "unknown
error" appears nowhere else in our tree, then that's an error code that
FormatMessage doesn't recognize. Anybod
Adrian Klaver schrieb am 26.05.2017 um 23:16:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/postgres-10/pgsql/lib/postgresql/pgxml.dll": unknown error 126
Apparently BigSQL forgot to include contrib/xml2 in their distribution;
you should ping them abo
On 05/26/2017 02:30 PM, Tom Lane wrote:
Adrian Klaver writes:
Well Thomas is using pg_upgrade from a BigSQL 10beta1 install to upgrade
from a 9.6 instance of unknown provenance. pg_upgrade is complaining
that the 9.6 cluster has pgxml.dll whereas the 10beta1 cluster does not
even though xml2 is
Adrian Klaver writes:
> Well Thomas is using pg_upgrade from a BigSQL 10beta1 install to upgrade
> from a 9.6 instance of unknown provenance. pg_upgrade is complaining
> that the 9.6 cluster has pgxml.dll whereas the 10beta1 cluster does not
> even though xml2 is installed on both clusters. The
On 05/26/2017 01:58 PM, Alvaro Herrera wrote:
Thomas Kellerer wrote:
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load
Thomas Kellerer wrote:
> Tom Lane schrieb am 26.05.2017 um 20:18:
> > > I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
> > > distribution) to upgrade a 9.6 cluster.
> > > pg_upgrade --check fails with the following messages:
> >
> > > could not load library "$libdir/pgxml
Tom Lane schrieb am 26.05.2017 um 20:18:
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
could not load library "$libdir/pgxml":
ERROR: could not load library
"d:/etc/po
Thomas Kellerer writes:
> I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
> distribution) to upgrade a 9.6 cluster.
> pg_upgrade --check fails with the following messages:
>could not load library "$libdir/pgxml":
>ERROR: could not load library
> "d:/etc/postgres-10/
I just tried pg_upgrade from the Postgres 10 Beta1 (from the BigSQL
distribution) to upgrade a 9.6 cluster.
pg_upgrade --check fails with the following messages:
Performing Consistency Checks
-
Checking cluster versions ok
Checking d
14 matches
Mail list logo
