| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Chris Hoover <revoohc(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: What happens on a commit? |
| Date: | 2007-05-23 14:18:00 |
| Message-ID: | 20070523141800.GJ4642@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Chris Hoover escribió:
> Ok, we are looking more into this. In the mean time, can someone please
> explain to me (or point me to the correct documentation) what happens in
> PostgreSQL when a commit is issued. What exactly does the database do?
It writes a commit WAL record and flushes (fsync) the WAL up to that
point. This is the more important bit. Also, async notifies are sent
(those you started with NOTIFY), and files corresponding to some
commands are deleted (e.g. TRUNCATE, CLUSTER, REINDEX). Temp tables
with ON COMMIT setting may be operated upon.
It entirely depends on what the transaction did.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Kramer | 2007-05-23 14:35:35 | Re: |
| Previous Message | Chris Hoover | 2007-05-23 14:13:51 | Re: What happens on a commit? |