| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Switching timeline over streaming replication |
| Date: | 2012-12-18 05:06:43 |
| Message-ID: | 50CFF9E3.8040605@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Since Thom already did the destruction test, I only chained 7 standbies,
just to see if I could reproduce his error.
In the process, I accidentally connected one standby to itself. This
failed, but the error message wasn't very helpful; it just gave me
"FATAL: could not connect, the database system is starting up". Surely
there's some way we could tell the user they've tried to connect a
standby to itself?
Anyway, I was unable to reproduce Thom's error. I did not see the
error message he did.
Without any read queries running on the standbys, lag from master to
replica7 averaged about 0.5 seconds, ranging between 0.1 seconds and 1.2
seconds.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Groshev Andrey | 2012-12-18 05:28:00 | Re: [GENERAL] trouble with pg_upgrade 9.0 -> 9.1 |
| Previous Message | Peter Eisentraut | 2012-12-18 03:48:38 | Re: Doc patch, put RAISE USING keywords into a table |