| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Why does slony use a cursor? Anyone know? |
| Date: | 2013-03-07 14:47:03 |
| Message-ID: | 5138A867.8010808@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/07/2013 08:23 AM, Kevin Grittner wrote:
> Exactly what version was this? Just about any queuing system (and
> this definitely includes Slony and some JMS implementations) were
> vulnerable to an autovacuum bug fixed with this patch from Jan
> Wieck:
Hmm. It's a 9.1.7 release, so if the latest is 9.1.8, that might be it.
It would explain why my contrived scenario in stage couldn't replicate
it, too. I'm going to see if I can trigger this behavior in stage by
creating a bunch of dead tuples in the slony log table while it's working.
Thanks, Kevin!
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eduardo Morras | 2013-03-07 14:50:58 | Re: Gitorious |
| Previous Message | Adrian Klaver | 2013-03-07 14:40:38 | Re: Password Security Standarts on PostgreSQL |