ansfer all data from A into B.
Can I daisy-chain streaming replication? In other words, temporarily
setup replication like this:
A ==> B ==> C
And after the transfer is done, just remove A from the scheme.
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing lis
Nevermind, this was fixed with:
ssl_renegotiation_limit = 0
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
his in the logs:
###
2015-11-03 21:45:31.885 UTC,,,3391,,56391e57.d3f,19,,2015-11-03 20:51:35
UTC,,0,LOG,0,"checkpoint starting: xlog",""
2015-11-03 21:45:35.400 UTC,,,4773,,56392a26.12a5,1,,2015-11-03 21:41:58
UT
resql-bdr-client-9.49.4.4-1trusty
amd64front-end programs for PostgreSQL-BDR 9.4
ii postgresql-bdr-contrib-9.4 9.4.4-1trusty
amd64additional facilities for PostgreSQL
ii postgresql-bdr-server-dev-9.49.4.4-1trusty
er rebuilding it from
scratch, under the old name?
Do I have to change the name every time I re-join a node?
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
http://packages.2ndquadrant.com/bdr/apt/pool/main/b/bdr-plugin/
Looks like the repo has not caught up to the latest 0.9.3 release. Would
it be possible to push updated packages to the repo, please? It would be
a great help with testing BDR.
Thanks,
--
Florin Andrei
http://florin.myip.org
_nodes;
TRUNCATE TABLE bdr.bdr_connections;
BEGIN;
SET LOCAL bdr.permit_unsafe_ddl_commands = true;
SET LOCAL bdr.skip_ddl_locking = true;
SECURITY LABEL FOR 'bdr' ON DATABASE bdrdemo IS '{"bdr": false}';
COMMIT;
-- Restart PG service.
-- To drop test database:
DRO
ty
postgresql-bdr-contrib-9.4 9.4.4-1trusty
postgresql-bdr-server-dev-9.4 9.4.4-1trusty
It's very useful to have these packages available, helps a lot with
testing, kudos to everyone involved.
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-g
it a while
bdrdemo=# DROP TABLE t1bdr;
ERROR: No peer nodes or peer node count unknown, cannot acquire DDL
lock
HINT: BDR is probably still starting up, wait a while
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
mpletely, so that those workers are laid to
rest and never respawn?
Basically, how do I reset BDR completely? It seems to retain the memory
of the bdrdemo database somewhere.
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 2015-09-15 16:45, Florin Andrei wrote:
On 2015-08-25 18:29, Craig Ringer wrote:
On 26 August 2015 at 07:19, Florin Andrei
wrote:
What do I need to do to start over? I want to delete all traces of
the BDR
configuration I've done so far.
you need to DROP the database you removed,
On 2015-08-25 18:29, Craig Ringer wrote:
On 26 August 2015 at 07:19, Florin Andrei
wrote:
What do I need to do to start over? I want to delete all traces of the
BDR
configuration I've done so far.
you need to DROP the database you removed, then re-create it as a new
empty database
sly, TRUNCATE is blocked until the long
SELECT finishes.
I'm looking for ways to avoid the conflict. One way would be to do
incremental updates to the users table - that's not an option yet.
What if I rename the users table to users_MMDD? Would that still be
blocked by SELECT? If
is already a member of a BDR group
HINT: Connect to the node you wish to add and run bdr_group_join from
it instead
What do I need to do to start over? I want to delete all traces of the
BDR configuration I've done so far.
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-gene
so).
As load balancer, PgPool-II might be what you're looking for.
Would there be any issues if I just used an ELB pointing at two masters?
Let's say I use sticky sessions to avoid clients switching masters too
much.
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql
On 2015-08-23 06:56, Martín Marqués wrote:
El 21/08/15 a las 20:45, Florin Andrei escribió:
The single instance scheme is not very reliable. I need to build a new
DB backend. I'll set up Postgres 9.4. Ideally, I'd like to setup 2
instances, each instance placed in a different availab
g all analytics on
the other node, what would be the best replication technique in this
case?
(We are also considering a migration from the batch update model to a
more continuous stream.)
--
Florin Andrei
http://florin.myip.org/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
On Mon, 2005-04-11 at 03:28 +0200, Daniel Verite wrote:
> Florin Andrei wrote:
>
> > On MySQL, it's enough to do this:
> >
> > GRANT ALL PRIVILEGES ON dbname.* TO username [IDENTIFIED BY 'password'];
> >
> > On PostgreSQL, you have to g
relname||' TO
username;' FROM pg_class c JOIN pg_namespace n ON (n.oid=c.relnamespace)
WHERE c.relkind='S' AND n.nspname='public';" | psql -d dbname
It seems to work fine on pgsql version 8.
Of course, after creating new tables and stuff, you may have to re-run
19 matches
Mail list logo
