Обсуждение: Website request -- developer docs along with release docs
Could I request that a link to the developer docs be posted along with the release docs on http://www.postgresql.org/docs/manuals/ ? First -- it is interesting. Second, if one is running CVS HEAD for testing (always a service to the community, if not your data), they are the appropriate docs. Finally, it gives users a chance to see why they might want to upgrade (for example by browsing the awesome windowing capabilities, etc). And yes, I could write a patch,... Tx On Mon, Oct 27, 2008 at 8:50 AM, Eric Haszlakiewicz <erh@swapsimple.com> wrote: > On Sun, Oct 19, 2008 at 11:21:09PM -0400, Tom Lane wrote: >> Eric Haszlakiewicz <erh@swapsimple.com> writes: >> > On Sun, Oct 19, 2008 at 10:15:22PM -0400, Tom Lane wrote: >> >> What platform is this, anyway? >> > I'm running on NetBSD 4. >> >> > Well, it seems that something doesn't work right with the "try the next key" >> > code when the userid are the same. I'm not really sure what I should try >> > here. >> >> I read the code and the shmget spec a bit more. It looks to me like the >> issue may be about the ordering of error checks in the kernel. The >> Single Unix Spec quoth > ...snip... >> If you are starting the two servers with different shmem sizing >> parameters then it is possible that the second reason for giving EINVAL >> applies. Now our code is expecting to get EEXIST if there's a shmem > ...snip... >> So the first question for you is did you give the two servers different >> shmem sizing parameters? If so, does the behavior change if you start >> them in the opposite order? If the answer to both is "yes" then I think >> you ought to file a bug against NetBSD kernel. They're returning an >> error code that is uselessly confusing and out of step with other >> implementations. > > Yes, and yes. The error checking order in NetBSD put the EEXIST return > last so the "different size check" was taking precedence. I fixed that, > and now starting two pg servers, even in different chroot's, behaves as > expected. Thanks for the suggestion of where to look! > > eric > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >
http://developer.postgresql.org/pgdocs/postgres/index.html On Mon, Oct 27, 2008 at 12:11 PM, Webb Sprague <webb.sprague@gmail.com> wrote: > Could I request that a link to the developer docs be posted along with > the release docs on > > http://www.postgresql.org/docs/manuals/ > > ? > > First -- it is interesting. Second, if one is running CVS HEAD for > testing (always a service to the community, if not your data), they > are the appropriate docs. Finally, it gives users a chance to see why > they might want to upgrade (for example by browsing the awesome > windowing capabilities, etc). > > And yes, I could write a patch,... > > Tx > > On Mon, Oct 27, 2008 at 8:50 AM, Eric Haszlakiewicz <erh@swapsimple.com> wrote: >> On Sun, Oct 19, 2008 at 11:21:09PM -0400, Tom Lane wrote: >>> Eric Haszlakiewicz <erh@swapsimple.com> writes: >>> > On Sun, Oct 19, 2008 at 10:15:22PM -0400, Tom Lane wrote: >>> >> What platform is this, anyway? >>> > I'm running on NetBSD 4. >>> >>> > Well, it seems that something doesn't work right with the "try the next key" >>> > code when the userid are the same. I'm not really sure what I should try >>> > here. >>> >>> I read the code and the shmget spec a bit more. It looks to me like the >>> issue may be about the ordering of error checks in the kernel. The >>> Single Unix Spec quoth >> ...snip... >>> If you are starting the two servers with different shmem sizing >>> parameters then it is possible that the second reason for giving EINVAL >>> applies. Now our code is expecting to get EEXIST if there's a shmem >> ...snip... >>> So the first question for you is did you give the two servers different >>> shmem sizing parameters? If so, does the behavior change if you start >>> them in the opposite order? If the answer to both is "yes" then I think >>> you ought to file a bug against NetBSD kernel. They're returning an >>> error code that is uselessly confusing and out of step with other >>> implementations. >> >> Yes, and yes. The error checking order in NetBSD put the EEXIST return >> last so the "different size check" was taking precedence. I fixed that, >> and now starting two pg servers, even in different chroot's, behaves as >> expected. Thanks for the suggestion of where to look! >> >> eric >> >> -- >> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-hackers >> > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >
Webb Sprague wrote: > Could I request that a link to the developer docs be posted along with > the release docs on > > http://www.postgresql.org/docs/manuals/ they are already referenced in the development section of the website: http://www.postgresql.org/developer/testing I'm not sure we actively should put them on the same page as the release docs - I could imagine people getting confused about that. > > ? > > First -- it is interesting. Second, if one is running CVS HEAD for > testing (always a service to the community, if not your data), they > are the appropriate docs. Finally, it gives users a chance to see why > they might want to upgrade (for example by browsing the awesome > windowing capabilities, etc). well to get -HEAD one has likely go the the development/testing section of the website and btw windowing functions are not yet in :-) Stefan
Thanks to all for the link.\ > they are already referenced in the development section of the website: They are actually a little difficult to find for those of us that don't use that section frequently, or at least finding a navigation page to that section. > I'm not sure we actively should put them on the same page as the release > docs - I could imagine people getting confused about that. How about a vote? I don't think postgres admins are that, ahem, unsophisticated. We could put them in <blink> if we had to ;)
am Mon, dem 27.10.2008, um 19:01:14 +0100 mailte Stefan Kaltenbrunner folgendes: > Webb Sprague wrote: > >Could I request that a link to the developer docs be posted along with > >the release docs on > > > >http://www.postgresql.org/docs/manuals/ > > they are already referenced in the development section of the website: > > http://www.postgresql.org/developer/testing > > I'm not sure we actively should put them on the same page as the release > docs - I could imagine people getting confused about that. I think - no. Mark this as dev-docu, but i think, this is a nice feature. Sometimes I'm searching the doc for the next version ( okay, i know where i can find this ), but i'm sure, somebody can't find this docu. The docu for the next version is definitively more important as the docu for, for instance, 7.4 ( this are available via http://www.postgresql.org/docs/manuals/). Regards, Andreas -- Andreas Kretschmer Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header) GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net
A. Kretschmer wrote: > > they are already referenced in the development section of the website: > > > > http://www.postgresql.org/developer/testing > I think - no. Mark this as dev-docu, but i think, this is a nice > feature. +1 -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>> > they are already referenced in the development section of the website: >> > >> > http://www.postgresql.org/developer/testing >> I think - no. Mark this as dev-docu, but i think, this is a nice >> feature. > +1 I think what we're talking about is adding a clearly-marked link to the dev docs somewhere on this page: http://www.postgresql.org/docs/ If so, +1. ...Robert