| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zubkovsky, Sergey" <Sergey(dot)Zubkovsky(at)transas(dot)com> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: pg_total_relation_size() and CHECKPOINT |
| Date: | 2008-03-13 20:20:30 |
| Message-ID: | 439.1205439630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
"Zubkovsky, Sergey" <Sergey(dot)Zubkovsky(at)transas(dot)com> writes:
> I've detected that a result value of pg_total_relation_size() for an
> actively updated table might be significantly differ from a result that
> is returned after explicit CHECKPOINT command execution.
Uh, can you show a specific example of what you mean?
> I understand the reasons of such behavior: cache buffers must be flushed
> in order to be sure that pg_total_relation_size() result will be like we
> expect.
I wouldn't think so. The space for a page is allocated immediately when
needed --- its *contents* might not be up to date, but that shouldn't
affect pg_total_relation_size.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zubkovsky, Sergey | 2008-03-14 15:23:22 | Re: pg_total_relation_size() and CHECKPOINT |
| Previous Message | Zubkovsky, Sergey | 2008-03-13 19:49:58 | pg_total_relation_size() and CHECKPOINT |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-03-13 20:24:17 | Re: aclitem out/in don't "work" |
| Previous Message | Tom Lane | 2008-03-13 20:18:13 | Re: aclitem out/in don't "work" |