I am new to bg_workers so this may be my user error,
but when I build and run the contrib/worker_spi
extension, I find that :
. starting postgres with the extension named in shared_preload_libraries :
its _PG_init is invoked as expected but no process is started -
it is as thou
r process in 9.4.4
> From: michael.paqu...@gmail.com
> To: johnlu...@hotmail.com
> CC: pgsql-general@postgresql.org
>
> On Tue, Jun 16, 2015 at 3:58 AM, John Lumby wrote:
>> I am new to bg_workers so this may be my user error,
>> but when I build and run the contrib/
t C/48D0
LOCATION: StartupXLOG, xlog.c:6700
Is the invalid record length msg anything to worry about?
But this method is purely empirical. Is it robust? Anyone have any better
recommendations?
Cheers, John Lumby
(**Note this log was from a pre-release 9.5, 9.5alpha2
I don't hav
RAL] how to switch old replication Master to new
> Standby after promoting old Standby
> To: johnlu...@hotmail.com
> CC: pgsql-general@postgresql.org
>
> On Mon, Mar 14, 2016 at 6:28 PM, John Lumby
> mailto:johnlu...@hotmail.com>> wrote:
>
> From: johnlu...@hotma
failed, then treat your old Primary as an
empty cluster
and commission it from the start as described next
Cheers, John Lumby
> Date: Mon, 14 Mar 2016 23:46:28 +0100
> Subject: Re: [GENERAL] Re: how to switch old replication Master to new
>
---
> Subject: Re: [GENERAL] Re: how to switch old replication Master to new
> Standby after promoting old Standby
> To: johnlu...@hotmail.com; michael.paqu...@gmail.com
> CC: oleksandr.shul...@zalando.de; pgsql-general@postgresql.org
> From: adrian.kla...@aklaver.com
&
shul...@zalando.de;
> adrian.kla...@aklaver.com
>
> On Tue, Mar 15, 2016 at 5:14 PM, John Lumby wrote:
>> But my question is, given that the divergence point was 2B60,
>> why is it looking for a file earlier than that?
>
> (please do not top-post, this is annoying as it
does postgresql xlogger just chop each WAL segment at the physical page
boundary?
Cheers, John Lumby
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
This topic came up before
http://archives.postgresql.org/pgsql-general/2010-12/msg00542.php
and there was some discussion on how-to.
Briefly, the table is partitioned and there is an id column declared as
id bigint DEFAULT nextval('history_id_seq'::regclass) NOT NULL
and the application
I would like to use an UPDATE RULE to modify the action performed
when any UPDATE is attempted on a certain table,
*including* an UPDATE which would fail because of no rows matching the WHERE.
Is this at all possible? I have tried with variations of ALSO|INSTEAD etc
but the RULE is never inv
___
> From: pavan.deola...@gmail.com
> Date: Fri, 31 Aug 2012 11:09:42 +0530
> Subject: Re: [GENERAL] UPDATE RULE to be invoked when UPDATE .. WHERE fails
> the WHERE predicate ?
>
> On Thu, Aug 30, 2012 at 6:31 PM, John Lumby
> mailto:
> Date: Mon, 3 Sep 2012 09:31:21 +0100
> Subject: Re: [GENERAL] UPDATE RULE to be invoked when UPDATE .. WHERE fails
> the WHERE predicate ?
> From: dean.a.rash...@gmail.com
> To: johnlu...@hotmail.com
> CC: pgsql-general@postgresql.org; pavan.deola...@
12 matches
Mail list logo
