[BUGS] Bug #540: pg_dump a simple table can fail if other view/triggers are faulty
luby liao ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description pg_dump a simple table can fail if other view/triggers are faulty Long Description We use Postgresql 7.1.2 on a Redhat 7.0 Linux PC. My CS145 students all work in a database called cs145. Some students introduced unintended faulty views and triggers into the database. When a student tried to pg_dump his own tables, he got error messages that say that other people's views or triggers were faulty. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Bug #540: pg_dump a simple table can fail if other
On Sun, 16 Dec 2001 [EMAIL PROTECTED] wrote: > luby liao ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > pg_dump a simple table can fail if other view/triggers are faulty > > Long Description > We use Postgresql 7.1.2 on a Redhat 7.0 Linux PC. My CS145 students > all work in a database called cs145. Some students introduced > unintended faulty views and triggers into the database. When a > student tried to pg_dump his own tables, he got error messages that > say that other people's views or triggers were faulty. We're going to need some additional information for this to be a complete report. What options were used to pg_dump, how far the dump got and what messages were reported. It'd be nice to know what was meant by faulty views and triggers or an example to reproduce the problem. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Bug #540: pg_dump a simple table can fail if other
Stephan Szabo <[EMAIL PROTECTED]> writes: > We're going to need some additional information for this to be a > complete report. It doesn't really require investigation. pg_dump pulls the entire schema before deciding what parts of it need to be dumped; therefore schema-level problems are likely to cause pg_dump to error out even if that part of the schema theoretically didn't need to be examined. I am disinclined to invest any effort in changing this, in part because I doubt it could be changed without making it impossible to do other things that we want to do in the near future (cf. nearby discussion about dumping sequences associated with the target table). regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
On Saturday 15 December 2001 03:06, Tom Lane wrote: > [EMAIL PROTECTED] writes: > > Hmm. Looks like there is a pg_operator entry for text[] = text[], > but none for bpchar[] = bpchar[]. This is an oversight, nothing more. > Feel free to add such an entry --- it can point to the same array-equals > function as the one for text[]. > > It's too late to fix this in the standard catalogs for 7.2, but I'll > make a note for 7.3. Suitable for 7.2.1? + Justin > > 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]) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
Justin <[EMAIL PROTECTED]> writes: > On Saturday 15 December 2001 03:06, Tom Lane wrote: >> It's too late to fix this in the standard catalogs for 7.2, but I'll >> make a note for 7.3. > Suitable for 7.2.1? Nyet. We don't do initdbs for dot-releases. Sometime in the future, it might be nice to devise a scheme that allows additions to the system catalogs (as opposed to fundamental changes) without an initdb. But we haven't got it today. 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
Re: [BUGS] Unable to compare _bpchar for similarity in WHERE-clause
> On Saturday 15 December 2001 03:06, Tom Lane wrote: > > [EMAIL PROTECTED] writes: > > > > > Hmm. Looks like there is a pg_operator entry for text[] = text[], > > but none for bpchar[] = bpchar[]. This is an oversight, nothing more. > > Feel free to add such an entry --- it can point to the same array-equals > > function as the one for text[]. > > > > It's too late to fix this in the standard catalogs for 7.2, but I'll > > make a note for 7.3. > > Suitable for 7.2.1? Nope, only minor stuff or 7.2.X and this would be a system table change anyway. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
