Fix src/backend/storage/smgr/README
Started by Fabrízio de Royes Melloover 11 years ago2 messages
Hi all,
Small fix in src/backend/storage/smgr/README about where is assigned fork
numbers.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
Show quoted text
Timbira: http://www.timbira.com.br
Blog sobre TI: http://fabriziomello.blogspot.com
Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
Twitter: http://twitter.com/fabriziomello
Attachments:
fix_storage_smgr_readme.patchtext/x-diff; charset=US-ASCII; name=fix_storage_smgr_readme.patchDownload
diff --git a/src/backend/storage/smgr/README b/src/backend/storage/smgr/README
index 12df42a..37ed40b 100644
--- a/src/backend/storage/smgr/README
+++ b/src/backend/storage/smgr/README
@@ -50,7 +50,7 @@ independently of the main data file, while still treating it all as a single
physical relation in system catalogs.
It is assumed that the main fork, fork number 0 or MAIN_FORKNUM, always
-exists. Fork numbers are assigned in src/include/storage/relfilenode.h.
+exists. Fork numbers are assigned in src/include/common/relpath.h.
Functions in smgr.c and md.c take an extra fork number argument, in addition
to relfilenode and block number, to identify which relation fork you want to
access. Since most code wants to access the main fork, a shortcut version of
Re: Fix src/backend/storage/smgr/README
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello@gmail.com> writes:
Small fix in src/backend/storage/smgr/README about where is assigned fork
numbers.
Ah, looks like I missed that reference when I moved the enum :-(.
Thanks, will fix.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers