On 13 May 2015 at 09:29, Wayne E. Seguin wrote:
> *awesome*, the question was for my own curiosity so thanks for this!
>
No worries.
I know it's trite, but for internal-ish detail like that the best reference
remains the source code. I'd like to think the sources are fairly sane.
--
Craig
*awesome*, the question was for my own curiosity so thanks for this!
On Tue, May 12, 2015 at 18:27 Craig Ringer wrote:
> On 12 May 2015 at 22:21, Wayne E. Seguin wrote:
>
>> Craig,
>>
>> It's alive!!!
>>
>> One more question on this thread, where can I find the meanings of
>> node_status in the
On 12 May 2015 at 22:21, Wayne E. Seguin wrote:
> Craig,
>
> It's alive!!!
>
> One more question on this thread, where can I find the meanings of
> node_status in the documentation?
>
node_status is really internal, but it's covered briefly in the docs:
http://bdr-project.org/docs/stable/catalo
Craig,
It's alive!!!
One more question on this thread, where can I find the meanings of
node_status in the documentation?
pgbdr=# SELECT * FROM bdr.bdr_nodes;
node_sysid | node_timeline | node_dboid | node_status | node_name
|node_local_dsn |
Craig,
I was starting the first node then letting all of the other nodes join as
quick as they could which clearly won't work. It also explains why it
worked when I did it manually, I can only do it sequentially myself ;) I
had suspected a race condition and it seems I was in the right area :)
Th
Craig, thank you so much for the quick response!
Adding these cleanup functions sounds wonderful, thank you for looking into
that.
One question, why template0 vs template1 ? (My guess is because you want it
to be devoid of pretty much everything?)
On Tue, May 12, 2015 at 1:31 AM, Craig Ringer w
On 12 May 2015 at 14:36, Wayne E. Seguin wrote:
> Also,
>
> Is there a way to remove these things from the init target node easier?
>
> d= p=504 a=ERROR: 55000: previous init failed, manual cleanup is required
> d= p=504 a=DETAIL: Found bdr.bdr_nodes entry for bdr
> (6147869128174526660,1,16908
On 12 May 2015 at 14:33, Wayne E. Seguin wrote:
>
>
7. on nodes 1-4 I am doing (adjusted for the nodes IP):
> SELECT bdr.bdr_group_join(
> local_node_name := 'pgbdr1',
> node_external_dsn := 'host=10.244.2.6 port=5432 user=postgres
> dbname=pgbdr',
> join_using_dsn := 'host=10.244
Also, what is the proper way to locate and remove these replication slots
as mentioned in this log?
On Mon, May 11, 2015 at 11:36 PM, Wayne E. Seguin
wrote:
> Also,
>
> Is there a way to remove these things from the init target node easier?
>
> d= p=504 a=ERROR: 55000: previous init failed, man
Also,
Is there a way to remove these things from the init target node easier?
d= p=504 a=ERROR: 55000: previous init failed, manual cleanup is required
d= p=504 a=DETAIL: Found bdr.bdr_nodes entry for bdr
(6147869128174526660,1,16908,) with state=i in remote bdr.bdr_nodes
d= p=504 a=HINT: Remo
To the wonderful BDR folks,
I have a 5 node pg+bdr cluster that I've spun up. I have verified that each
node can connect via psql to each other node. I am having an issue creating
the bdr group and having the nodes join each other.
The steps I am taking are as follows (I used pg compiled using ge
11 matches
Mail list logo
