Re: [GENERAL] WAL's listing in pg_xlog by some sql query

2016-06-07 Thread Michael Paquier
On Mon, Jun 6, 2016 at 9:51 PM, Stephen Frost wrote: > * Vik Fearing (v...@2ndquadrant.fr) wrote: >> On 03/06/16 04:32, Michael Paquier wrote: >> > On Fri, Jun 3, 2016 at 11:23 AM, Sameer Kumar >> > wrote: >> >> On Fri, Jun 3, 2016 at 4:30 AM Stephen Frost wrote: >> >>> Given the usefulness of

[GENERAL] High availability and load balancing ...

2016-06-07 Thread Sunil N Shinde
Hi, I need to do the setup for High availability function. Also want to implement load balancing for 02 nodes. I think PGPool will be require for that. Can I use PGPool without cost. Can I get the basic steps to do this setup? Database-- Postgresql 9.1

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread Adrian Klaver
On 06/07/2016 03:22 PM, Patrick B wrote: One more question guys... Does the pg_basebackup re-write the data? or do I have to have free space? Like.. the DB is 2 TB.. do I have to have more 2TB? or it will use those 2TB that already are there? I would suggest taking a tour of: https://www.pos

Re: [GENERAL] PL/PGSQL + inserts+updates+limit - Postgres 9.3

2016-06-07 Thread Patrick B
Thanks Adrian... it's working ;)

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread Patrick B
One more question guys... Does the pg_basebackup re-write the data? or do I have to have free space? Like.. the DB is 2 TB.. do I have to have more 2TB? or it will use those 2TB that already are there? cheers

[GENERAL] BDR Custom Conflict Handler

2016-06-07 Thread Elijah Bitting
There appears to be absolutely zero documentation regarding the expected format of a custom conflict handler function. I'm attempting to define a custom conflict handler for a test bdr cluster. When I tried to register a generic function with no parameters I get a somewhat useful error message

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread Patrick B
Anyway.. will do the pg_basebackup and see how it goes... cheers guys Patrick 2016-06-08 8:41 GMT+12:00 Patrick B : > yep.. pg_basebackup the problem is that the servers are in a > different country.. and the DB is 2TB > > the pg_basebackup will probably fail and I'll have to do a DUMP as I'

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread Patrick B
yep.. pg_basebackup the problem is that the servers are in a different country.. and the DB is 2TB the pg_basebackup will probably fail and I'll have to do a DUMP as I've already done with another slave time ago

Re: [GENERAL] Postgres Dropped DB have recovered files how to restore

2016-06-07 Thread Alvaro Herrera
John R Pierce wrote: > On 6/6/2016 4:09 PM, Alvaro Herrera wrote: > >I have no idea about Windows filesystems but you may be able to > >"undelete" the files, as long as you don't touch the partition for > >anything else; search the web for "undelete ntfs". Once you undelete > >you will need to put

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread bricklen
On Mon, Jun 6, 2016 at 5:32 PM, Patrick B wrote: > My set up: > > > Master --> slave01 (streaming replication) --> slave02 (streaming > replication) > Master --> slave03 (wal_files 4 days old, not streaming replication) > > The wal_files are stored into each server. > But when the slave03 was dow

Re: [GENERAL] Re-sync slave server

2016-06-07 Thread Adrian Klaver
On 06/06/2016 05:32 PM, Patrick B wrote: My set up: Master --> slave01 (streaming replication) --> slave02 (streaming replication) Master --> slave03 (wal_files 4 days old, not streaming replication) The wal_files are stored into each server. But when the slave03 was down, the wal_files weren'

Re: [GENERAL] PL/PGSQL + inserts+updates+limit - Postgres 9.3

2016-06-07 Thread Adrian Klaver
On 06/06/2016 09:01 PM, Patrick B wrote: Ok so guys CREATE or REPLACE FUNCTION function_data_1() RETURNS SETOF bigint AS $$ declare row record; BEGIN [...] FOR row IN EXECUTE ' SELECT

[GENERAL] 2 node bdr setup gives error in replication slots

2016-06-07 Thread Nikhil
I am getting below error in my 2 node BDR setup. postgres going down. any idea? <35382016-06-07 10:16:59 GMT%LOG: database system was interrupted; last known up at 2016-06-07 09:06:44 GMT <35382016-06-07 10:16:59 GMT%PANIC: replication slot file "pg_replslot/bdr_16389_6293051490331141125_2_16389