Hi Guillaume,
With your v2 patch, -B options working as expected but --no-blobs
options is still unrecognized, this happens is because of you have
forgot to add entry for 'no-blobs' in long_options[] array.
Apart from this concern patch looks good to me. Thanks
Regards,
Amul
The new status of t
Dear all,
I'd like to ask for help or advice with choosing the best replication setup for
my task.
I need to listen to continuous inserts/deletes/updates over a set of tables,
and serve them over http, so I would like to off-load this procedure to a
separate slave machine. I thought that logical
On Wed, Nov 2, 2016 at 11:58 PM, Andy Halsall wrote:
> Can we assume that the 9.6 libpq library is backwards compatible with
> applications compiled against 9.3 headers? I wouldn't expect to have to
> re-compile our application against 9.6 libpq headers and redeploy because
> we're not taking adva
Hi,
I found, in pg_xlog dir, several WAL segment files with old modification
timestamp but with their names greater than more recent files.
Ex.:
000100C6 modified today
000100DE modified yesterday
I thought it could not be possible.
I'm doing some tests w
On 11/3/16 12:28 PM, Tom DalPozzo wrote:
Hi,
I found, in pg_xlog dir, several WAL segment files with old modification
timestamp but with their names greater than more recent files.
Ex.:
000100C6 modified today
000100DE modified yesterday
This is complet
On Thu, Nov 03, 2016 at 11:28:57AM +0100, Tom DalPozzo wrote:
> What am I missing?
David already explained, but you might want to read also:
https://www.depesz.com/2011/07/14/write-ahead-log-understanding-postgresql-conf-checkpoint_segments-checkpoint_timeout-checkpoint_warning/
depesz
--
The b
Hi,
so if I understand right, the ...DE file's previous name, was less than
...C6, then it was renamed in big advance for later use. I was missing this
advance.
Thanks!
Pupillo
2016-11-03 11:45 GMT+01:00 hubert depesz lubaczewski :
> On Thu, Nov 03, 2016 at 11:28:57AM +0100, Tom DalPozzo wrote:
On 11/02/2016 11:18 PM, Gionatan Danti wrote:
Il 03-11-2016 00:21 Jim Nasby ha scritto:
On 11/2/16 2:02 PM, Gionatan Danti wrote:
That means at least some of the Postgres files have been damaged
(possibly due to the failing disk). Postgres will complain when it
sees internal data structures tha
Hi,
2016-11-03 8:22 GMT+01:00 amul sul :
> Hi Guillaume,
>
> With your v2 patch, -B options working as expected but --no-blobs
> options is still unrecognized, this happens is because of you have
> forgot to add entry for 'no-blobs' in long_options[] array.
>
>
You're right. v3 (attached) fixes t
On 11/3/16 1:16 PM, Tom DalPozzo wrote:
so if I understand right, the ...DE file's previous name, was less than
...C6, then it was renamed in big advance for later use. I was missing
this advance.
That is correct.
--
-David
da...@pgmasters.net
--
Sent via pgsql-general mailing list (pgsql-g
Hi Guillaume,
I found following issues with this patch, sorry missed in previous post:
#1 :
43 @@ -392,6 +393,10 @@ main(int argc, char **argv)
44 dopt.outputBlobs = true;
45 break;
46
47 + case 'B': /* Don't dump blobs */
48 +
11 matches
Mail list logo
