A while back I was talking to Jan about what our plans should be for
slony.info.
The user base and use-cases for slony been replaced with options built
around the built in replication/decoding features and these are present in
all non EOL versions of PG.
The only updates to slony in the
On Mon, 27 Nov 2023, Sebastien Marchand via Slony1-general wrote:
Hello,
I have a problem that I've just noticed on several of my replications,
my sl_log_1 table no longer empties and keeps incrementing. Where should
I look to find the event that breaks the function that's supposed to
manage
The Slony team is pleased to announce Slony 2.2.11 the next minor release
of the Slony 2.2.x series
Slony 2.2.11 includes the following changes
- Add support for PG 15
- Remove standard_conforming_strings autoconf check
- Fix typo in admin guide
Slony 2.2.11 can be downloaded from the
On Wed, 19 Jan 2022, Tim Kane via Slony1-general wrote:
The REL_2_2_10 is now in the git repo.
I just skipped the step of pushing it.
I wouldn't wait for the warning to be removed.
The next time I do a release for an actual change/fix I'll update the
warning versions then.
Steve
I notice
On Mon, 6 Dec 2021, Andy Dossett via Slony1-general wrote:
Hi
ￜ
Is Slony 2.2.10 fully compatible with Postgres 14, or is there a 2.2.11 in the
pipeline?
As far as I know it should work.
I ran the slony testsuite against PG14 during the beta period and found no
issues.
If you
On Fri, 22 Oct 2021, Sung Hsin Lei via Slony1-general wrote:
This question may have been asked already. I have noticed that if it takes 10
days for the initial data transfer to complete, if the transfer
is interrupted after 9 days, the transfer resumes from day 1. In other words, I
need 10
On Wed, 26 May 2021, Sebastien Marchand via Slony1-general wrote:
Hi,
thank you, but i don't know how do this, my server A can't talk to my server
C...
I might misunderstand what your trying to do but does
store path(server=1, client=2, conninfo='serverA.local');
store path(server=2,
On Thu, 21 Jan 2021, Richard Yen via Slony1-general wrote:
On Wed, Jan 20, 2021 at 8:55 PM 張 蔚捷（Zhang WeiJie） via Slony1-general
wrote:
But I hove no idea how to change to the following mode.
node 1->node2
node 1->node3
Any suggestions would be greatly appreciated.
The Slony team is pleased to announce Slony 2.2.10 the next minor release
of the Slony 2.2.x series
Slony 2.2.10 includes the following changes
- Remove unsupported warning on PG13
This change was supposed to be included in 2.2.9 but the warning was still
present.
Slony 2.2.10 can be
On Sun, 29 Nov 2020, Steve Singer via Slony1-general wrote:
Just as a heads up.
The unsupported warning is still printed by 2.2.9 with PG13(but no longer
with PG 12). It still should work. We'll remove that warning on PG13 with
2.2.10
The Slony team is pleased to announce Slony 2.2.9
The Slony team is pleased to announce Slony 2.2.9 the next minor release
of the Slony 2.2.x series
Slony 2.2.9 includes the following changes
- Compile with -fno-common by default. Fix
compile errors caused by defining variables in headers
- Adjust slonik_build_env.pl so it works with
On Thu, 23 Jul 2020, Sung Hsin Lei via Slony1-general wrote:
Hello,
I have a slave machine who's database I want to restore on a different machine
with a different ip. Since the backup process takes several hours, I disconnect
the master,
backup the slave db and restore it on the new slave
On Mon, 8 Jun 2020, Fontana Daniel C (Desartec S.R.L.) via Slony1-general wrote:
Are the slon proceses running?
I think they get started as windows services (once you add those services)
Are they logging any errors (or anything else) to the windows event logs?
Hi i am trying to do my first
On Wed, 8 Apr 2020, zayasj1 wrote:
The merge sets completed. We have slony running on both sides
(production/failover). We're using PostgreSQL
9.4.
When I am looking in pgAdmin, and I go down to Slony Replication and start
looking at my clusters, I can see
"Nodes" and "Replication sets".
On Wed, 8 Apr 2020, zayasj1 via Slony1-general wrote:
I want to confirm a few things first
Your are saying that you have two clusters, $CLUSTER was set to 'cluster1'
and 'cluster2'.
and when you do
select * from _cluster1.sl_set;
you see your two sets
and
select * from _cluster2.sl_set;
On Thu, 26 Mar 2020, Sebastien Marchand via Slony1-general wrote:
Hi,
I've got a replication fully fonctionnal, but after a big update of
datas, the master doesn't succeed to sent all datas ( 7gB ) because
their line is too bad ( 60kB/s UP ).
Can i set an option to sent less data in one
On Wed, 25 Mar 2020, Rajni Baliyan via Slony1-general wrote:
Hello folks,
I need some pointers and recommendations regarding Slony and PostgreSQL
minor/major version upgrade.
Also, I can't see any document which lists the changes from 2.2.4 to 2.2.8.
On 2/28/20 12:28 PM, John Muehlhausen via Slony1-general wrote:
Hello,
It appears that native streaming and logical replication in postgres
disallows the use of NOTIFY on the master (fired by a trigger)
propagating to a LISTENer on a slave. (In the former case it is not
implemented, and in
18 matches
Mail list logo
