Re: [DOCS] Error message listing?
Tom Lane writes: > Or were you looking for src/include/utils/errcodes.h ? I think we should put such a list in the documentation, at least for those error codes that we have really assigned. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [DOCS] duplicated index entry found ...
Tom Lane writes: > The Hermit Hacker <[EMAIL PROTECTED]> writes: > > duplicated index entry found, CHARACTER STRINGS LENGTH > > duplicated index entry found, LENGTH CHARACTER STRINGS > > duplicated index entry found, SUBSTRING > > duplicated index entry found, SUBSTRING > > 4 entries ignored... > > Yeah, I've been seeing that for quite some time, but haven't been able > to figure out what it's complaining about. Surely multiple index > entries for the same term are legal, so what's its beef? Since by default (which we don't override) an index entry points to its nearest containing section (rather than directly to its occurence), if a section contains the same index entry more than once, it does indeed look like a duplicate on the outside. There are at least two obvious ways to get rid of the warnings, but I could never figure out the benefits and drawbacks of them. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Error message listing?
The point of including the message texts is for people supporting various versions who are looking directly at the message texts for earlier versions. This also allows them to upgrade the error handling to use the new error codes instead of relying on the message text (which is what we want). elein On Fri, Aug 08, 2003 at 09:21:51AM -0400, Tom Lane wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > Tom Lane writes: > >> Or were you looking for src/include/utils/errcodes.h ? > > > I think we should put such a list in the documentation, at least for those > > error codes that we have really assigned. > > I have no objection to that. I have doubts about the utility of a > listing of message texts, but the SQLSTATE codes seem reasonable to > document. > > Would it be possible to generate the list automatically from errcodes.h, > to simplify future maintenance? > > regards, tom lane > > ---(end of broadcast)--- > TIP 7: don't forget to increase your free space map settings > ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] Error message listing?
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane writes: >> Or were you looking for src/include/utils/errcodes.h ? > I think we should put such a list in the documentation, at least for those > error codes that we have really assigned. I have no objection to that. I have doubts about the utility of a listing of message texts, but the SQLSTATE codes seem reasonable to document. Would it be possible to generate the list automatically from errcodes.h, to simplify future maintenance? regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [DOCS] Error message listing?
Tom, > Or were you looking for src/include/utils/errcodes.h ? More or less. The issue is that many projects have internal code to handle PG error messages by parsing them for certain text. The overhaul of message handling is going to break that code; users need to know what the new messages and/or codes are before migrating. -- -Josh Berkus __AGLIO DATABASE SOLUTIONS___ Josh Berkus Complete information technology [EMAIL PROTECTED] and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Error message listing?
The issue is that many projects have internal code to handle PG error messages by parsing them for certain text. The overhaul of message handling is going to break that code; users need to know what the new messages and/or codes are before migrating. I concur, I have such an application and it would be really useful to have the new error messages and codes. Cheers --- Francois Home page: http://www.monpetitcoin.com/ "Would Descartes have programmed in Pascal?" - Umberto Eco ---(end of broadcast)--- TIP 3: 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: [DOCS] Error message listing?
The issue is that many projects have internal code to handle PG error messages by parsing them for certain text. The overhaul of message handling is going to break that code; users need to know what the new messages and/or codes are before migrating. I concur, I have such an application and it would be really useful to have the new error messages and codes. Cheers --- Francois Home page: http://www.monpetitcoin.com/ "Would Descartes have programmed in Pascal?" - Umberto Eco ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] Error message listing?
Josh Berkus <[EMAIL PROTECTED]> writes: > Am I missing something here? We're preparing for migration, but I > can't find anywhere a centralized list of the new error messages. Is > it in the source somewhere? If so, can we add it to the > documentation? You could make one by running gettext --- see http://developer.postgresql.org/docs/postgres/nls.html#AEN55720 I do not especially see the point of adding such a list to the documentation, however. Or were you looking for src/include/utils/errcodes.h ? regards, tom lane ---(end of broadcast)--- TIP 3: 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
[DOCS] Error message listing?
Folks, Am I missing something here? We're preparing for migration, but I can't find anywhere a centralized list of the new error messages. Is it in the source somewhere? If so, can we add it to the documentation? -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] duplicated index entry found ...
The Hermit Hacker <[EMAIL PROTECTED]> writes: > duplicated index entry found, CHARACTER STRINGS LENGTH > duplicated index entry found, LENGTH CHARACTER STRINGS > duplicated index entry found, SUBSTRING > duplicated index entry found, SUBSTRING > 4 entries ignored... Yeah, I've been seeing that for quite some time, but haven't been able to figure out what it's complaining about. Surely multiple index entries for the same term are legal, so what's its beef? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
