Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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.

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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

Re: [GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 10

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 >

[GENERAL] Postgres 10 Beta1 - pg_upgrade fails on Windows 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

Re: [GENERAL] pg_dump 8.3.3 ERROR: invalid page header in block 2264419 of relation "pg_largeobject"

On 5/25/17 6:30 AM, Tom Lane wrote: David Wall writes: They do have a slave DB running via WAL shipping. Would that likely help us in any way? Have you tried taking a backup from the slave? It's possible that the corruption exists only on the master. We will give this a

Re: [GENERAL] COPY: row is too big

doganmeh writes: > I tried varchar(12) also, nothing changed. My questions is 1) I have > 672x12=8,064 characters in the first row (which are actually the headers), > why would it complain that it is 8760. No, you have 672*13, because each varchar value will require a length

Re: [GENERAL] COPY: row is too big

Am 26.05.2017 um 14:07 schrieb doganmeh: I tried varchar(12) also, nothing changed. My questions is 1) I have 672x12=8,064 characters in the first row (which are actually the headers), why would it complain that it is 8760. I am assuming here type `text` occupies 1 byte for a character.

Re: [GENERAL] COPY: row is too big

Hello > -Original Message- > From: pgsql-general-ow...@postgresql.org > [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of doganmeh > Sent: Freitag, 26. Mai 2017 14:08 > To: pgsql-general@postgresql.org > Subject: Re: [GENERAL] COPY: row is too big > > I am piggy-backing in this

Re: [GENERAL] COPY: row is too big

On 05/26/2017 05:07 AM, doganmeh wrote: I am piggy-backing in this thread because I have the same issue as well. I need to import a csv file that is 672 columns long and each column consists of 12 alpha-numeric characters. Such as: SA03ARE1015DSA03ARE1S15NSB03ARE1015D ... 356412

Re: [GENERAL] COPY: row is too big

BTW, we have pg9.5 run on ubuntu. -- View this message in context: http://www.postgresql-archive.org/COPY-row-is-too-big-tp5936997p5963386.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To

Re: [GENERAL] COPY: row is too big

I am piggy-backing in this thread because I have the same issue as well. I need to import a csv file that is 672 columns long and each column consists of 12 alpha-numeric characters. Such as: SA03ARE1015DSA03ARE1S15NSB03ARE1015D ... 356412 275812 43106 ... I am aware