Hi all,
I have a similar problem.
OS Red Hat Enterprise Linux Server release 6.6.
Postgresql packets were installed from repository as described in
https://wiki.postgresql.org/wiki/BDR_Packages
postgresql-bdr94-bdr-0.8.0beta1-1_2ndQuadrant.el6.x86_64
postgresql-bdr94-contrib-9.4.0_bdr1-1_2ndQua
OK, so you're on 0.7.1.
Before we pursue much more, can you please update to bdr-plugin/next ? The
0.8.0 release is pending shortly, and contains a lot of changes since
0.7.1, some of which pertain to init behaviour.
After 0.7.1 the structure was changed a bit. So you will need to first
check out
Hi Chris
When running: git rev-parse --short HEAD
Output: a63674e
The source package I got from:
git clone git://git.postgresql.org/git/2ndquadrant_bdr.git
git clean -d -fx ""
git checkout bdr/0.7.1
This is the logs from node 1:
d= p=28495 a=LOCATION: ExecAlterExtensionStmt, extension.c:27
On 23 January 2015 at 08:22, agent wrote:
> Hi Craig I have a similar issue with a rather small number of servers
> involved.
>
OK. That looks odd.
What revision are you running exactly?
git rev-parse --short HEAD
please.
Also, correponding logs from the other two nodes please.
Hi CraigI have a similar issue with a rather small number of servers
involved.*Node 1:*max_replication_slots = 4max_wal_senders = 6wal_level =
'logical'track_commit_timestamp = onshared_preload_libraries =
'bdr'max_worker_processes = 10log_error_verbosity = verboselog_min_messages
= debug1log_line_
That's a lot of databases and explains why the logs were so busy.
For the purpose of testing it would be interesting to simplify this case
down, if you can, to the minimum required to reproduce the issue. It's
awfully hard to keep track of what's going on with this many concurrent
operations - esp
Hi Andres,
Any other conf should I list in addition to the bdr settings below?
BDR Settings(replaced the real db name here):
1. on node 01, the replication src one:
# Generic settings required for BDR
max_replication_slots = 60
max_wal_senders = 60
wal_level = 'logical'
track_commit_timestamp
Hi,
On 2015-01-13 02:43:26 -0700, deans wrote:
> Hi Craig, any insight on this issue? :)
You've, afaics, not posted your configuration. Could you do so?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training &
:( not yet, still having the issue.
--
View this message in context:
http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5834821.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make ch
Hi Dean
Did you manage do get any help. I am having the exact issue at the moment.
--
View this message in context:
http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5834722.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mail
Hi Craig, any insight on this issue? :)
Thanks,
Dean
--
View this message in context:
http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5833722.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@postgres
Thanks Craig.
> How exactly do you restart the node?
Using "service postgresql-9.4 restart" command to do the service restart.
> Please show the full log line, not just an excerpt, along with the lines
> around
it.
> If possible run with log_error_verbosity=verbose and show the extra line(s)
pri
On 01/07/2015 11:28 AM, deans wrote:
> Hi Guys.
>
> First of all, BDR is cool, should have tried it earlier.
>
> Environment: CentOS 6.5, PostgreSQL 9.4.0 with BDR from yum repository
>
> Done the PostgreSQL 9.4 with BDR setup successfully by following the User
> Guide and Admin Doc, but got a i
13 matches
Mail list logo
