| From: | Craig Ringer <craig(at)2ndQuadrant(dot)com> |
|---|---|
| To: | 张柏年 <zhangbonian(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: flush buffer after connection disllowed |
| Date: | 2012-11-20 12:32:56 |
| Message-ID: | 50AB7878.6060209@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/20/2012 06:09 PM, 张柏年 wrote:
> Hi All,
>
> If there is command to flush the internal buffer within
> Postgresql server of specific database after all connections has been
> disconnected to that database?
>
Why?
It isn't clear what problem you are trying to solve.
The write buffers and WAL are global across the cluster (group of
databases), they're not per-database. So you can't really flush just one
database as far as I know.
You shouldn't generally need to do any kind of explicit flushing anyway.
That's why a commit fsync()s.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dinesh kumar | 2012-11-20 13:45:26 | Re: PG_TERMINATE_BACKEND not working. |
| Previous Message | aasat | 2012-11-20 12:30:55 | fetch from cursor in pg_stats_activity and related SQL query |