| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <markokr(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Add relation fork support to pg_relation_size() function. |
| Date: | 2008-10-06 10:32:39 |
| Message-ID: | 48E9E947.7030708@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Gregory Stark wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Heikki Linnakangas wrote:
>>> If we go with the ".fsm" extension, we'll get "12345.fsm.1" when the FSM
>>> grows large enough to be segmented. Does anyone have a problem with a
>>> filename with two dots? Shouldn't be a problem, I guess.
>
> We could also just do 12345_fsm.1 like we do now but with the symbolic name.
or 12345fsm.1. I think 12345.fsm.1 looks the best.
FWIW, with the defaults of 8k block size and 1GB segments, the table
needs to be over 4TB in size until the FSM file needs to be segmented.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2008-10-06 10:48:50 | Re: pgsql: Add relation fork support to pg_relation_size() function. |
| Previous Message | Gregory Stark | 2008-10-06 08:32:32 | Re: pgsql: Add relation fork support to pg_relation_size() function. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-10-06 10:46:21 | Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement |
| Previous Message | Guillaume Lelarge | 2008-10-06 09:33:16 | Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement |