Re: [BUGS] Bug #890: only one user per process in libpq with krb5 auth

I don't think any of that has changed, if that is what you are asking. --- Ed Schaller wrote: -- Start of PGP signed section. > > OK, please let me know. Thanks. > > I haven't taken the time to check the current state of t

Re: [BUGS] Bug #890: only one user per process in libpq with krb5 auth

OK, please let me know. Thanks. --- Ed Schaller wrote: -- Start of PGP signed section. > > Is this ready to be applied. It looks fine to me. I want to remove the > > part of the patch that keeps the old structure definiti

Re: [BUGS] Solution for bug #899

Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Laurent FAILLIE wrote: > Ok there is the

Re: [BUGS] Bug #904: Deallocating of prepared statement in ECPG at

Can someone comment on this bug report? --- [EMAIL PROTECTED] wrote: > Jiri Langr ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > Deallocating of

Re: [BUGS] Problem with RULE to update tables

Sean Reifschneider <[EMAIL PROTECTED]> writes: > I've tried this on both 7.3 and 7.2.3, and am running into an odd > problem. Basically I have one table that is a count of available and one > that has allocations against that. I wanted to use rules to auto-update the > available count, and everyt

[BUGS] Bug #912: pg_restore cannot restore individual rule from custom dump

Joseph Tate ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description pg_restore cannot restore individual rule from custom dump Long Description pg_restore can restore individual triggers and tables, but cannot restore individual rules.

[BUGS] Bug #911: pg_dump/pg_restore fails when using triggers/rules on tables including large objects

Joseph Tate ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description pg_dump/pg_restore fails when using triggers/rules on tables including large objects Long Description If a table has a large object referenced in a column, but also has

[BUGS] strange behaviour of extended ascii characters (LATIN1)

To [EMAIL PROTECTED] Name: Ennio Iannucci Email Address:[EMAIL PROTECTED] Severity: Minor Annoyance (but great curiosity) Short Description: special characters (beyond ascii char(127)) seem to behave ina very strange way in a postgresql table. THE FACTS: = I created a pg table from a *.tx

[BUGS] Problem with RULE to update tables

I've tried this on both 7.3 and 7.2.3, and am running into an odd problem. Basically I have one table that is a count of available and one that has allocations against that. I wanted to use rules to auto-update the available count, and everything works fine as long as I do deletes one-by-one...

[BUGS] pg_dumpall segfault

POSTGRESQL BUG REPORT TEMPLATE Your name : Nick Eskelinen Your email address : [EMAIL PR

Re: [BUGS] pg_dumpall segfault

Ahh... as a matter of fact I do. Adding someone to this empty group corrects the problem. Thanks! Nick On Fri, Mar 14, 2003 at 05:32:42PM -0500, Tom Lane wrote: > Nick Eskelinen <[EMAIL PROTECTED]> writes: > > pg_dumpall segfaults when trying to dump group information. > > Hmm, you have any empt

Re: [BUGS] Bug #902: Build problems with 7.3.1 and 7.3.2 on SunOS (crypt.h)

Patch attached and applied. Thanks. Should I backpatch to 7.3.X? Is it safe? --- [EMAIL PROTECTED] wrote: > Fred Houweling ([EMAIL PROTECTED]) reports a bug with a severity of 3 > The lower the number the more severe it is