Re: Fix mdsync never-ending loop problem
От
Alvaro Herrera
Тема
Re: Fix mdsync never-ending loop problem
Дата
Msg-id
20070405134524.GB8578@alvh.no-ip.org
Ответ на
Fix mdsync never-ending loop problem (Heikki Linnakangas)
Список
Дерево обсуждения
Fix mdsync never-ending loop problem Heikki Linnakangas <heikki@enterprisedb.com>
Re: Fix mdsync never-ending loop problem Alvaro Herrera <alvherre@commandprompt.com>
Re: Fix mdsync never-ending loop problem Tom Lane <tgl@sss.pgh.pa.us>
Re: Fix mdsync never-ending loop problem Tom Lane <tgl@sss.pgh.pa.us>
Re: Fix mdsync never-ending loop problem Heikki Linnakangas <heikki@enterprisedb.com>
Re: Fix mdsync never-ending loop problem Tom Lane <tgl@sss.pgh.pa.us>
Re: Fix mdsync never-ending loop problem Heikki Linnakangas <heikki@enterprisedb.com>
Re: Fix mdsync never-ending loop problem Tom Lane <tgl@sss.pgh.pa.us>
Re: Fix mdsync never-ending loop problem Heikki Linnakangas <heikki@enterprisedb.com>
Re: Fix mdsync never-ending loop problem "Simon Riggs" <simon@2ndquadrant.com>
Re: Fix mdsync never-ending loop problem Heikki Linnakangas <heikki@enterprisedb.com>
While skimming over this I was baffled a bit about the usage of (InvalidBlockNumber - 1) as value for FORGET_DATABASE_FSYNC. It took me a while to realize that this code is abusing the BlockNumber typedef to pass around *segment* numbers, so the useful range is much smaller and thus the usage of that value is not a problem in practice. I wonder if it wouldn't be better to clean this up by creating a separate typedef for segment numbers, with its own special values? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-patches по дате отправления