| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | basti <mailinglist(at)unix-solution(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: November 2013 Replication Data Loss Issue |
| Date: | 2014-03-17 09:05:14 |
| Message-ID: | 5326BACA.7030002@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 03/17/2014 10:57 AM, basti wrote:
> we have a database master Version:
> PostgreSQL 9.1.6 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-2) 4.7.2, 64-bit
> and a WAL-Replication Slave with hot-standby version:
> PostgreSQL 9.1.9 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit.
>
> Since a few days we had problems with the Linux OOM-Killer.
> Some simple query that normally take around 6-7 minutes now takes 5 hours.
> We did not change any configuration values the last days.
>
> Are we affected by this bug:
> https://wiki.postgresql.org/wiki/Nov2013ReplicationIssue ?
No. Per the wiki page:
> Who is at risk for this issue?
>
> Users who:
>
> are on one of the following PostgreSQL versions: 9.3.0, 9.3.1, 9.2.5, 9.1.10, and 9.0.14. Earlier versions are not affected.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Voinea | 2014-03-17 11:09:20 | Re: BUG #5465: dblink TCP connection hangs blocking translation from being terminated |
| Previous Message | basti | 2014-03-17 08:57:14 | November 2013 Replication Data Loss Issue |