| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Standby Feedback should default to on in 9.3+ |
| Date: | 2012-11-30 20:49:51 |
| Message-ID: | CAGTBQpYyO3RjXmwsY21FhVpG-czrttoaU7STUJKMjWArYrxyGQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 30, 2012 at 5:46 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
>
> Think of someone setting up a test server, by setting it up as a standby
> from the master. Now, when someone holds a transaction open in the test
> server, you get bloat in the master. Or if you set up a standby for
> reporting purposes - a very common use case - you would not expect a long
> running ad-hoc query in the standby to bloat the master. That's precisely
> why you set up such a standby in the first place.
Without hot standby feedback, reporting queries are impossible. I've
experienced it. Cancellations make it impossible to finish any
decently complex reporting query.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-30 20:59:10 | Re: Hot Standby Feedback should default to on in 9.3+ |
| Previous Message | Tom Lane | 2012-11-30 20:47:59 | Re: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger? |