[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
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
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
