From: | Satoshi Nagayasu <snaga(at)uptime(dot)jp> |
---|---|
To: | Mike Levine <mikenyy3(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Where in the source code does postgres write to disk? |
Date: | 2013-04-20 16:30:14 |
Message-ID: | 5172C296.6080405@uptime.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
2013/04/21 0:01, Mike Levine wrote:
> According
> tohttp://www.postgresql.org/docs/9.2/static/storage-file-layout.html
>
> "When a table or index exceeds 1 GB, it is divided into gigabyte-sized
> segments. The first segment's file name is the same as the filenode;
> subsequent segments are named filenode.1, filenode.2, etc."
>
> I was wondering where in the source code this is dealt with. I have been
> searching for the last few hours but have had no luck
>
>
> Any help guiding me to the location in the source code where postgres
> writes the buffer to disk would be greatly appreciated.
See mdextend() in src/backend/storage/smgr/md.c.
That's the code which deals with segment files on extending a table,
and RELSEG_SIZE defines the segment size, 1GB by default.
Regards,
--
Satoshi Nagayasu <snaga(at)uptime(dot)jp>
Uptime Technologies, LLC. http://www.uptime.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2013-04-20 22:24:00 | Re: UPDATE with subquery; possible bug in query parser? |
Previous Message | Scott Parkerson | 2013-04-20 16:27:51 | UPDATE with subquery; possible bug in query parser? |