On Sat, Feb 11, 2017 at 9:56 AM, Andrea Urbani wrote:
> I'm a beginner here... anyway I try to share my ideas.
>
> My situation is changed in a worst state: I'm no more able to make a pg_dump
> neither with my custom fetch value (I have tried "1" as value = one row at
> the
I'm a beginner here... anyway I try to share my ideas.
My situation is changed in a worst state: I'm no more able to make a pg_dump
neither with my custom fetch value (I have tried "1" as value = one row at the
time) neither without the "--column-inserts":
pg_dump: Dumping the contents of
On Fri, Jan 20, 2017 at 12:52 AM, Andrea Urbani wrote:
> I have used "custom" parameters because I want to decrease the fetch size
> only on the tables with big bloab fields. If we remove the
> "custom-fetch-table" parameter and we provide only the "fetch-size" parameter
>
nd maybe more clear.
Well, how to go on? I add it to the commitfest and somebody will decide and fix
it?
Please, let me know
Thank you
Andrea
Sent: Wednesday, December 21, 2016 at 6:44 PM
From: "Stephen Frost" <sfr...@snowman.net>
To: "Andrea Urbani" <matfan...@m
Andrea,
* Andrea Urbani (matfan...@mail.com) wrote:
>I had a problem with a Postgresql 9.3.5 on 32 bit linux, old 2.6.26
>kernel:
Ok, though, to be clear, this is a feature request, so we wouldn't
back-patch adding this to pg_dump.
>I have solve it adding two new parameters,
Hello to everybody,
I had a problem with a Postgresql 9.3.5 on 32 bit linux, old 2.6.26 kernel:
Program: pg_dump
Problem: if you have tables with big blob fields and you try to dump them with --inserts you could get errors like
pg_dump: [archiver (db)] query failed: lost synchronization