On 15 June 2015 at 17:19, Sylvain MARECHAL wrote:
> Is it possible to completely detach a node so that it can live alone
Yes. On a different node to the one you want to remove,
bdr.bdr_part_by_node_names(ARRAY['the_node_to_remove']) to safely
remove it without disrupting the other nodes.
> in p
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/worker_spi
> extension,I find that :
>
> . starting postgres with the extension named in shared_preload_libraries :
> its _PG_init is invo
On Mon, 15 Jun 2015 17:48:54 -0300
Anderson Valadares wrote:
> 2015-06-12 19:56 GMT-03:00 Bill Moran :
>
> > Please do not remove the mailing list from replies. See below.
> >
> > On Fri, 12 Jun 2015 09:21:19 -0300
> > Anderson Valadares wrote:
> >
> > > 2015-06-08 20:33 GMT-03:00 Bill Moran :
2015-06-12 19:56 GMT-03:00 Bill Moran :
>
> Please do not remove the mailing list from replies. See below.
>
> On Fri, 12 Jun 2015 09:21:19 -0300
> Anderson Valadares wrote:
>
> > 2015-06-08 20:33 GMT-03:00 Bill Moran :
> >
> > > On Mon, 8 Jun 2015 11:59:31 -0300
> > > Anderson Valadares wrote:
On Fri, Jun 12, 2015 at 7:27 PM, Steve Kehlet wrote:
> Just wanted to report that I rolled back my VM to where it was with 9.4.2
> installed and it wouldn't start. I installed 9.4.4 and now it starts up just
> fine:
>
>> 2015-06-12 16:05:58 PDT [6453]: [1-1] LOG: database system was shut down
>>
On 06/15/2015 11:44 AM, James Cloos wrote:
"AK" == Adrian Klaver writes:
AK> So what is at line 508 in /etc/postgresql/9.3/main/postgresql.conf?
timezone = 'localtime'
That is the same in the 9.4 conf, where everything defaults to utc as I
desire.
Went back to the beginning of the thread:
> "OE" == Oliver Elphick writes:
OE> localtime is a timezone but it appears simply to be a copy of the
OE> current local timezone file in /etc/localtime. (This is a binary file
OE> containing a timezone file.)
OE> Is that file different between machines?
It is 9.3 vs 9.4 on the same box.
O
> "AK" == Adrian Klaver writes:
AK> So from the command line on the non-UTC machine what does the below show:
AK> ~>date
It is the same machine, just the old 9.3 cluster vs the new 9.4 cluster.
date returns: Mon Jun 15 19:37:14 UTC 2015
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED
On 15/06/15 20:44, James Cloos wrote:
>> "AK" == Adrian Klaver writes:
>
> AK> So what is at line 508 in /etc/postgresql/9.3/main/postgresql.conf?
>
> timezone = 'localtime'
>
> That is the same in the 9.4 conf, where everything defaults to utc as I
> desire.
>
> Those are Debian's default
On 06/15/2015 11:44 AM, James Cloos wrote:
"AK" == Adrian Klaver writes:
AK> So what is at line 508 in /etc/postgresql/9.3/main/postgresql.conf?
timezone = 'localtime'
That is the same in the 9.4 conf, where everything defaults to utc as I
desire.
So from the command line on the non-UTC ma
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
Tom Lane-2 wrote
> The assumption is that the histogram represents a
> continuous distribution of values in which no one value occurs often
> enough to be interesting (if it did, it would be in the MCV list...).
> Therefore it does not matter much whether any specific histogram entry
> is exactly "
> "AK" == Adrian Klaver writes:
AK> So what is at line 508 in /etc/postgresql/9.3/main/postgresql.conf?
timezone = 'localtime'
That is the same in the 9.4 conf, where everything defaults to utc as I
desire.
Those are Debian's default config files. As I wrote the diff between
the not worki
On 06/15/2015 10:55 AM, James Cloos wrote:
The full results on that cluster of select * from pg_settings where name =
'TimeZone' is:
-[ RECORD 1 ]---
name | TimeZone
setting| localtime
unit |
category | Client Connecti
The full results on that cluster of select * from pg_settings where name =
'TimeZone' is:
-[ RECORD 1 ]---
name | TimeZone
setting| localtime
unit |
category | Client Connection Defaults / Locale and Formatting
short_de
Andres Freund wrote:
> A first version to address this problem can be found appended to this
> email.
>
> Basically it does:
> * Whenever more than MULTIXACT_MEMBER_SAFE_THRESHOLD are used, signal
> autovacuum once per members segment
> * For both members and offsets, once hitting the hard limi
use this query:
SELECT
CASE
WHEN pg_last_xlog_receive_location() = pg_last_xlog_replay_location() THEN 0
ELSE EXTRACT (EPOCH FROM now() - pg_last_xact_replay_timestamp())::INTEGER
END
AS replication_lag;
found at
http://www.postgresql.org/message-id/cadkbjjwz9m0swpt3oqe8f9+tfd4-f54ue6xtkh4nerpv
Hello all,
Is it possible to completely detach a node so that it can live alone, in
particular that DDL are again possible on that node?
I tried with a simple node without success:
<<<
postgres=# create database test template template0;
CREATE DATABASE
postgres=# \c test
You are now connected
18 matches
Mail list logo
