| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Dbsize backend integration |
| Date: | 2005-07-03 16:10:28 |
| Message-ID: | 4696.1120407028@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Dawid Kuroczko <qnex42(at)gmail(dot)com> writes:
> Oh, I think pg_dbfile_size is best so far.
I think it's by far the ugliest suggestion yet :-(
Andreas's suggestion of having just one function with a bool parameter
might be a workable compromise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-07-03 16:14:38 | Re: PATCH to allow concurrent VACUUMs to not lock each |
| Previous Message | Tom Lane | 2005-07-03 16:02:38 | Re: contrib/pgcrypto functions not IMMUTABLE? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-07-03 16:14:38 | Re: PATCH to allow concurrent VACUUMs to not lock each |
| Previous Message | Bernd Helmle | 2005-07-03 15:29:35 | ALTER OBJECT SET SCHEMA |