Re: [GENERAL] BDR

[Roland van Laar]

On 14-03-16 22:17, Dustin Kempter wrote:
Hello all, I am attempting to set up BDR between 2 separate nodes. I 
have been following the guide and got to here 
http://bdr-project.org/docs/0.9.0/quickstart-enabling.html

I am now stuck on this section

"Then you run a function that identifies a BDR group that delineates a 
connection string for other nodes to communicate with (for the first 
node, we will use port 5598) from the same SQL session as above on 
port 5598:


SELECT bdr.bdr_group_create(
  local_node_name := 'node1',
  node_external_dsn := 'port=5598 dbname=bdrdemo'
);"

However my instances are not on the same server and I attempted to 
simply add a host=(the ip) but that failed.

There are a couple of other factors:
- is postgres running on an external available ip?
- is there a replication user with a password?

Roland


Please help

Thanks in advance!







--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] BDR install broken on Ubuntu 14.04

[Roland van Laar]

On 13-01-16 17:48, LOUBRADOU, Rémy wrote:

Hi,

I have the same issue. It was working fine a month ago. I wrote a 
cookbook with chef to install BDR a month ago since then I did not 
change the cookbook but now I got this error.


This seem to be the heart of the issue:

Removing obsolete dictionary files:
==> ldev4:  * No PostgreSQL clusters exist; see "man pg_createcluster"
==> ldev4: /usr/share/postgresql-common/maintscripts-functions: line 
95: db_stop: command not found
==> ldev4: dpkg: error processing package postgresql-bdr-9.4 
(--configure):
==> ldev4:  subprocess installed post-installation script returned 
error exit status 127



Anyone know what's going on ? I'm going to investigate.


The debconf source file is missing.
db_stop, stands for debconf stop.

It is supposed to be fixed but it is not.
See this closed issue on Github: 
https://github.com/2ndQuadrant/bdr/issues/156


I "fixed" it in ansible by

- installing bdr accepting the fail
- removing the db_stop line
- installing bdr again.

This is the relevant part of my ansible configuration:

- name: install postgresql bdr
  apt:
name=postgresql-bdr-9.4-bdr-plugin
state=present
  ignore_errors: yes

- name: remove db_stop from postgres postinstall script
  lineinfile:
dest=/usr/share/postgresql-common/maintscripts-functions
regexp=db_stop
state=absent

- name: reinstall postgresql bdr to mitigate the db_stop problem
  apt:
name=postgresql-bdr-9.4-bdr-plugin
state=present

Regards,

Roland



Thanks for your replies,

Rémy





--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Exclude bdr data from dump

[Roland van Laar]

Hello,

I want to exclude all bdr data from a database dump.
My command is:

$ bdr_dump -Fp -h localhost -U postgres mydb -f /tmp/mydb.data 
--data-only --exclude-table='bdr*


This results in bdr data being included.

Including only bdr results in an error:

$ bdr_dump -Fp -h localhost -U postgres mydb -f /tmp/mydb.data 
--data-only --table='bdr*'

bdr_dump: No matching tables were found

Please help.

Roland



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Support for BDR in 9.5?

[Roland van Laar]

On January 8, 2016 7:42:06 PM GMT+01:00, "Andrew Biggs (adb)"  
wrote:
>On 1/8/16, 10:53 AM, Rob Sargent wrote:
>
>On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote:
>Can anyone tell me if PostgreSQL 9.5 supports (either natively or by
>extension) the BDR functionality?
>
>I tried it out and ran into issues, but it could well have been I was
>doing something wrong.
>
>Thanks!
>Andrew
>
>I'm sure those who might be able to help you would be interested in
>what, exactly, it was you tried.
>
>Installed 9.5 to CentOS7 via yum, and tried going through the BDR
>quick-start guide (minus sections 2.1):
>
>http://bdr-project.org/docs/stable/quickstart.html
>
>It was unhappy that BDR binaries were not on the path, and failed at
>section 2.4.
>
>Then went back and tried installing the BDR patch (section 2.1) which
>finished with this unhappy message:
>
>configure: error: bdr is not compatible with postgres 9.5
>
>I was just curious if others have had success with this.

Bdr is only compatible with 9.4 and needs the specific bdr postgres.

Roland
>
>Andrew



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] BDR install broken on Ubuntu 14.04

[Roland van Laar]

Hi,

I'm installing BDR on a ubuntu 14.04 (Trusty) machine. I can reproduce 
this error.

It happens locally with a new VM and on Digital ocean.
The error is:

/var/lib/dpkg/info/postgresql-bdr-9.4.postinst: 95: 
/var/lib/dpkg/info/postgresql-bdr-9.4.postinst: db_stop: not found


How can I fix this?

The full installation log is included below.

Regards,

Roland van Laar

sudo apt-get update
sudo apt-get upgrade
wget -qO - http://packages.2ndquadrant.com/bdr/apt/AA7A6805.asc |sudo 
apt-key add -
wget -qO - https://www.postgresql.org/media/keys/ACCC4CF8.asc |sudo 
apt-key add -
sudo add-apt-repository 'deb http://packages.2ndquadrant.com/bdr/apt/ 
trusty-2ndquadrant main'
sudo add-apt-repository 'deb http://apt.postgresql.org/pub/repos/apt/ 
trusty-pgdg main'

sudo apt-get update
sudo apt-get install postgresql-bdr-9.4-bdr-plugin


The full installation log:
$ sudo apt-get install postgresql-bdr-9.4-bdr-plugin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  linux-headers-3.13.0-57 linux-headers-3.13.0-57-generic
  linux-headers-3.13.0-61 linux-headers-3.13.0-61-generic
  linux-image-3.13.0-57-generic linux-image-3.13.0-61-generic
  linux-image-extra-3.13.0-57-generic linux-image-extra-3.13.0-61-generic
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libpq5 libxslt1.1 pgdg-keyring postgresql-bdr-9.4 
postgresql-bdr-client-9.4

  postgresql-bdr-contrib-9.4 postgresql-client-common postgresql-common
  ssl-cert
Suggested packages:
  oidentd ident-server locales-all postgresql-bdr-doc-9.4 libdbd-pg-perl
  openssl-blacklist
The following NEW packages will be installed:
  libpq5 libxslt1.1 pgdg-keyring postgresql-bdr-9.4
  postgresql-bdr-9.4-bdr-plugin postgresql-bdr-client-9.4
  postgresql-bdr-contrib-9.4 postgresql-client-common postgresql-common
  ssl-cert
0 upgraded, 10 newly installed, 0 to remove and 3 not upgraded.
Need to get 5,995 kB of archives.
After this operation, 28.4 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mirrors.digitalocean.com/ubuntu/ trusty/main libxslt1.1 
amd64 1.1.28-2build1 [145 kB]
Get:2 http://mirrors.digitalocean.com/ubuntu/ trusty/main ssl-cert all 
1.0.33 [16.6 kB]
Get:3 http://packages.2ndquadrant.com/bdr/apt/ trusty-2ndquadrant/main 
postgresql-bdr-client-9.4 amd64 9.4.5-1trusty [1,068 kB]
Get:4 http://packages.2ndquadrant.com/bdr/apt/ trusty-2ndquadrant/main 
postgresql-bdr-9.4 amd64 9.4.5-1trusty [3,677 kB]
Get:5 http://apt.postgresql.org/pub/repos/apt/ trusty-pgdg/main libpq5 
amd64 9.4.5-1.pgdg14.04+1 [122 kB]
Get:6 http://packages.2ndquadrant.com/bdr/apt/ trusty-2ndquadrant/main 
postgresql-bdr-contrib-9.4 amd64 9.4.5-1trusty [443 kB]
Get:7 http://packages.2ndquadrant.com/bdr/apt/ trusty-2ndquadrant/main 
postgresql-bdr-9.4-bdr-plugin amd64 0.9.3-1trusty [230 kB]
Get:8 http://apt.postgresql.org/pub/repos/apt/ trusty-pgdg/main 
pgdg-keyring all 2014.1 [5,898 B]
Get:9 http://apt.postgresql.org/pub/repos/apt/ trusty-pgdg/main 
postgresql-client-common all 171.pgdg14.04+1 [76.6 kB]
Get:10 http://apt.postgresql.org/pub/repos/apt/ trusty-pgdg/main 
postgresql-common all 171.pgdg14.04+1 [210 kB]

Fetched 5,995 kB in 1s (4,540 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libpq5:amd64.
(Reading database ... 146095 files and directories currently installed.)
Preparing to unpack .../libpq5_9.4.5-1.pgdg14.04+1_amd64.deb ...
Unpacking libpq5:amd64 (9.4.5-1.pgdg14.04+1) ...
Selecting previously unselected package libxslt1.1:amd64.
Preparing to unpack .../libxslt1.1_1.1.28-2build1_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.28-2build1) ...
Selecting previously unselected package pgdg-keyring.
Preparing to unpack .../pgdg-keyring_2014.1_all.deb ...
Unpacking pgdg-keyring (2014.1) ...
Selecting previously unselected package postgresql-client-common.
Preparing to unpack .../postgresql-client-common_171.pgdg14.04+1_all.deb ...
Unpacking postgresql-client-common (171.pgdg14.04+1) ...
Selecting previously unselected package postgresql-bdr-client-9.4.
Preparing to unpack 
.../postgresql-bdr-client-9.4_9.4.5-1trusty_amd64.deb ...

Unpacking postgresql-bdr-client-9.4 (9.4.5-1trusty) ...
Selecting previously unselected package ssl-cert.
Preparing to unpack .../ssl-cert_1.0.33_all.deb ...
Unpacking ssl-cert (1.0.33) ...
Selecting previously unselected package postgresql-common.
Preparing to unpack .../postgresql-common_171.pgdg14.04+1_all.deb ...
Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev 
by postgresql-common'

Unpacking postgresql-common (171.pgdg14.04+1) ...
Selecting previously unselected package postgresql-bdr-9.4.
Preparing to unpack .../postgresql-bdr-9.4_9.4.5-1trusty_amd64.deb ...
Unpacking postgresql-bdr-9.4 (9.4.5-1trusty) ...
Selecting previously unselected package postgresql-bdr-contrib-9.4.
Preparing to unpack

Re: [GENERAL] Code of Conduct: Is it time?

[Roland van Laar]

On January 5, 2016 5:47:16 PM GMT+01:00, "Joshua D. Drake" 
 wrote:
>Hello,
>
>I had a hard time writing this email. I think Code of Conducts are 
>non-essential, a waste of respectful people's time and frankly if you 
>are going to be a jerk, our community will call you out on it. 
>Unfortunately a lot of people don't agree with that. I have over the 
>course of the last year seen more and more potential users very 
>explicitly say, "I will not contribute to a project or attend a 
>conference that does not have a CoC".

Do they give a rational for that?
>
>Some of us may be saying, "Well we don't want those people". I can't 
>argue with some facts though. Ubuntu has had a CoC[1] since the 
>beginning of the project and they grew exceedingly quick. Having walls 
>in the hallway of interaction isn't always a bad thing.
>
>In reflection, the only thing a CoC does is put in writing what 
>behaviour we as a project already require, so why not document it and 
>use it as a tool to encourage more contribution to our project?
>
>Sincerely,
>
>JD
>
>
>1. http://www.ubuntu.com/about/about-ubuntu/conduct



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] Backup and Restore BDR databases

[Roland van Laar]

Hello,

I'm using BDR with master-master replication.  It works like a charm.

I have a question about backups and restoring them.
I use this script to backup my database: 
https://wiki.postgresql.org/wiki/Automated_Backup_on_Linux


However I'm getting problems with a pg_restore:

pg_restore -h localhost -U postgres -d exampledb -Fc exampledb.custom

That doesn't work when I restore it a database without bdr.
Restoring it to a bdr database needs a second postgres host because of 
the need for DDL locking.


However when using a second postgres host with a bdr enabled database 
I'm getting these errors.

For example:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 195; 1259 17229 
SEQUENCE auth_group_id_seq example
pg_restore: [archiver (db)] could not execute query: ERROR:  CREATE 
SEQUENCE ... increment is not supported for bdr sequences

Command was: CREATE SEQUENCE auth_group_id_seq
START WITH 1500
INCREMENT BY 1
MINVALUE 1500
NO MAXVALUE
CACHE 1
U...
pg_restore: [archiver (db)] could not execute query: ERROR: relation 
"auth_group_id_seq" does not exist

Command was: ALTER TABLE auth_group_id_seq OWNER TO exampledb;

pg_restore: [archiver (db)] Error from TOC entry 2521; 2604 17440 
DEFAULT id exampledb
pg_restore: [archiver (db)] could not execute query: ERROR: relation 
"django_migrations_id_seq" does not exist
Command was: ALTER TABLE ONLY django_migrations ALTER COLUMN id SET 
DEFAULT nextval('django_migrations_id_seq'::regclass);



and the restore process hangs.

All the tables are created on both, however there are no rows in them.

My question is, how can I backup and restore a postgres BDR database?

Regards,

Roland van Laar


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general