| From: | "Greg Stark" <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(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:48:50 |
| Message-ID: | 4136ffa0810060348s7990cb2by6c2d383b2a5b1775@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Oct 6, 2008 at 11:32 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
> 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.
Hm, so on the one hand people will just have 12345.1, 12345.2, ... and
12345.fsm which is kind of neat.
On the other hand if they do have a problem with multiple periods they
won't find out until they have a pretty big database already and are
kind of stuck. And our regression tests won't test it at all.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-06 12:02:35 | Re: pgsql: Add relation fork support to pg_relation_size() function. |
| Previous Message | Heikki Linnakangas | 2008-10-06 10:32:39 | Re: pgsql: Add relation fork support to pg_relation_size() function. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | iihero | 2008-10-06 11:42:51 | Re: About postgresql8.3.3 build in MS VS2005 |
| Previous Message | Heikki Linnakangas | 2008-10-06 10:46:21 | Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement |