Postgres skipped checking for duplicate tables due to some
timing issue. I don't want my DB to ending up hosed by something like that.
Thanks,
Rob
From: "David G. Johnston" <david.g.johns...@gmail.com>
Date: Thursday, May 18, 2017 at 3:31 PM
To: Rob Brucks <rob.bru...@racksp
eate table statement.
Thanks,
Rob
From: "David G. Johnston" <david.g.johns...@gmail.com>
Date: Thursday, May 18, 2017 at 3:05 PM
To: Rob Brucks <rob.bru...@rackspace.com>
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: [GENERAL
PostgreSQL 9.5.4 installed from PGDG packages on Centos 7.3.1611
· Zabbix 3.2 server
Thanks,
Rob Brucks
obr...@gmail.com>
Date: Thursday, February 23, 2017 at 9:23 AM
To: "David G. Johnston" <david.g.johns...@gmail.com>
Cc: Rob Brucks <rob.bru...@rackspace.com>, Tom Lane <t...@sss.pgh.pa.us>,
François Beaulieu <fr...@tzone.org>, Adrian Klaver <adrian.kla...@aklaver.c
Thank you Tom.
So, long-term, you don't see any negative impacts to the master cluster?
I just don't want to implement this as a streaming "push" mechanism and then
have my cluster crash in 12 months because it hit some obscure problem with
notifications.
This turned out to be a really
the
"pg_last_xact_replay_timestamp" on the slaves so we can more accurately monitor
replication lag on quiet systems.
Thanks,
Rob
On 2/21/17, 5:03 PM, "Tom Lane" <t...@sss.pgh.pa.us> wrote:
Rob Brucks <rob.bru...@rackspace.com> writes:
> If a notify is sent and then PG is
If a notify is sent and then PG is immediately shut down, wouldn't PG want to
save that message for processing after startup?
Or is the message just discarded?
--Rob
From: "David G. Johnston" <david.g.johns...@gmail.com>
Date: Tuesday, February 21, 2017 at 4:45 PM
To: Rob
orage. But I wonder if that file is only used to store
notify commands during shutdown/startup?
Or if there are any considerations for memory usage…
--Rob
On 2/21/17, 4:38 PM, "Adrian Klaver" <adrian.kla...@aklaver.com> wrote:
On 02/21/2017 02:19 PM, Rob Brucks wrote:
>
David G. Johnston" <david.g.johns...@gmail.com>
Date: Tuesday, February 21, 2017 at 3:38 PM
To: Adrian Klaver <adrian.kla...@aklaver.com>
Cc: Rob Brucks <rob.bru...@rackspace.com>, "pgsql-general@postgresql.org"
<pgsql-general@postgresql.org>
Subject: Re: [GE
.@aklaver.com> wrote:
On 02/21/2017 01:07 PM, Rob Brucks wrote:
> Hi All,
>
>
>
> I just wanted to check with you guys to make sure that constantly
> issuing "NOTIFY" commands without corresponding "LISTEN" commands will
>
ges inserted with nobody to listen for them, which is why I'm
posting here.
Do you see any long-term problems with constantly issuing "NOTIFY" commands
every 30 seconds without an associated "LISTEN" command?
Thank you,
Rob Brucks
L (without being a superuser) and alert when an
excessive number of WAL logs are waiting to be archived. That way intervention
can be performed before an out-of-space condition occurs.
I've implemented it as a separate function below, but would rather have it
built in to postgres.
Thanks,
Rob Bruck
I'd like to propose two enhancements to the PostgreSQL code, but I'm not sure
if this is the correct mailing list. So if it's not then please let me know
where I need to post this.
These are monitoring-centric enhancement requests since I'm trying to implement
accurate monitoring in a secure
13 matches
Mail list logo
