Re: [pgsql-patches] Lock compatibility matrix
> representations, both redundant with the textual description. I don't Docs patch is in SGML table representation, text view is a demonstration in mail. -- Teodor Sigaev E-mail: [EMAIL PROTECTED] WWW: http://www.sigaev.ru/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgsql-patches] Lock compatibility matrix
On Tue, 2007-01-30 at 21:33 +0100, Peter Eisentraut wrote: > Simon Riggs wrote: > > > Why would we want to have two redundant copies of the same > > > information? > > > > The lock information is not available anywhere in the form of a > > matrix. > > But it will be. A patch for the documentation has been proposed. Cool. When that's done, we probably don't need the code version. Would've been helpful if you'd explained what you meant... not many people read all posts on all lists. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgsql-patches] Lock compatibility matrix
Simon Riggs wrote: > > Why would we want to have two redundant copies of the same > > information? > > The lock information is not available anywhere in the form of a > matrix. But it will be. A patch for the documentation has been proposed. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgsql-patches] Lock compatibility matrix
"Simon Riggs" <[EMAIL PROTECTED]> writes: > On Tue, 2007-01-30 at 11:09 +0100, Peter Eisentraut wrote: >> Why would we want to have two redundant copies of the same information? > The lock information is not available anywhere in the form of a matrix. Sure, but at this point we have proposals for adding two different matrix representations, both redundant with the textual description. I don't mind adding one of the two, but both seems overkill. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgsql-patches] Lock compatibility matrix
On Tue, 2007-01-30 at 11:09 +0100, Peter Eisentraut wrote: > Pavan Deolasee wrote: > > I had this in a different form, but reworked so that it matches the > > doc patch that Teodor submitted earlier. I think it would be good to > > have this information in the lock.h file as well. > > Why would we want to have two redundant copies of the same information? The lock information is not available anywhere in the form of a matrix. I've personally found a matrix useful for application design, though that hasn't influenced Pavan's independent creation of exactly that. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [pgsql-patches] Lock compatibility matrix
On 1/30/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote: Pavan Deolasee wrote: > I had this in a different form, but reworked so that it matches the > doc patch that Teodor submitted earlier. I think it would be good to > have this information in the lock.h file as well. Why would we want to have two redundant copies of the same information? IMHO its useful to have this information in the source code, just like many other comments. It improves the readability of the code while documentation acts as a reference. But I am not sure whats the generally accepted practice for PostgresQL, so I may be wrong here. Thanks, Pavan -- EnterpriseDB http://www.enterprisedb.com
Re: [pgsql-patches] Lock compatibility matrix
Pavan Deolasee wrote: > I had this in a different form, but reworked so that it matches the > doc patch that Teodor submitted earlier. I think it would be good to > have this information in the lock.h file as well. Why would we want to have two redundant copies of the same information? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgsql-patches] Lock compatibility matrix
I had this in a different form, but reworked so that it matches the doc patch that Teodor submitted earlier. I think it would be good to have this information in the lock.h file as well. Thanks, Pavan -- EnterpriseDB http://www.enterprisedb.com lock-compatibility.patch Description: Binary data ---(end of broadcast)--- TIP 6: explain analyze is your friend
