Re: [BUGS] RC2 refuses to build if --infodir=foo is set

2003-11-13 Thread Troels Arvin
On Wed, 12 Nov 2003 23:13:38 -0500, Bruce Momjian wrote:

> We don't have any .info documentation.  Why should the option work?

Why should it be displayed when "./configure --help" is run, then?

-- 
Greetings from Troels Arvin, Copenhagen, Denmark



---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


[BUGS] plpgsql does not close cursors when a block ends

2003-11-13 Thread Marcel Gsteiger
Hi,

Please find enclosed my description of what I think is probably a bug
in plpgsql.

Keep up the good work, this is a wonderful product.

Best regards
Marcel Gsteiger
Milprog AG
3001 Berne
Switzerland

Freundliche GrĂ¼sse
Milprog AG
Marcel Gsteiger


bug.template
Description: Binary data
BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:Gsteiger, Marcel
TEL;WORK:+41 31 382 05 15
TEL;PREF;FAX:+41 31 382 33 04
EMAIL;WORK;PREF;NGW:[EMAIL PROTECTED]
N:Gsteiger;Marcel
ADR;INTL;WORK;PARCEL;POSTAL:;;Effingerstrasse 29;Berne;;CH-3008;Switzerland
LABEL;INTL;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Gsteiger, Marcel=0A=
Effingerstrasse 29=0A=
Berne  CH-3008=0A=
Switzerland
LABEL;DOM;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Gsteiger, Marcel=0A=
Effingerstrasse 29=0A=
Berne  CH-3008
TEL;PREF:+41 31 382 05 15
ORG:Milprog AG
END:VCARD


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


[BUGS]

2003-11-13 Thread Wade Klaver
Hello all,

  Just so this problem is logged in the system, I am making an overly vague 
bug report.  I have no nice method of repeating this as it requires a large 
database with somewhat broken RI to run for a long time before running VACUUM 
FULL ANALYZE;
I get:

dropsites=# vacuum full  analyze;
WARNING:  Rel pg_type: TID 12/46: InsertTransactionInProgress 27217603 - can't 
shrink relation
WARNING:  Rel pg_type: TID 12/47: InsertTransactionInProgress 27217603 - can't 
shrink relation
WARNING:  Rel pg_attribute: TID 152/1: InsertTransactionInProgress 27217603 - 
can't shrink relation
WARNING:  Rel pg_attribute: TID 152/2: InsertTransactionInProgress 27217603 - 
can't shrink relation
...
...
And so on.  The source code says "this should never happen".
This took place on the following system:
dropsites=# select version();
   version   
-
 PostgreSQL 7.3.2 on i386-unknown-freebsd4.6, compiled by GCC 2.95.4
(1 row)

[EMAIL PROTECTED] sendpage]$ uname -a
FreeBSD ***..com 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #0: Wed Sep 17 
11:18:42 PDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WAY2EASY  i386

Any more details you may request and I shall do my best to deliver.  I am 
currently trying to get this to happen on -STABLE, but to no avail.
Thanks all.

-- 
Wade Klaver
Wavefire Technologies Corporation
GPG Public Key at http://archeron.wavefire.com

/"\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
 X  - NO Word docs in e-mail .
/ \ -


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


Re: [BUGS] plpgsql does not close cursors when a block ends

2003-11-13 Thread Bruce Momjian
Marcel Gsteiger wrote:
> I created a plpgsql function declaring and then using a cursor.
> After opening and using this cursor, I forgot to close it.  Now
> when the function terminates, this cursor remains open.  Then,
> when I call the function again with other parameters, the OPEN
> CURSOR complains about the cursor declared within the function
> already being open.

The system is working as designed.

--
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [BUGS]

2003-11-13 Thread Tom Lane
Wade Klaver <[EMAIL PROTECTED]> writes:
> dropsites=# vacuum full  analyze;
> WARNING:  Rel pg_type: TID 12/46: InsertTransactionInProgress 27217603 - can't 
> shrink relation
> WARNING:  Rel pg_type: TID 12/47: InsertTransactionInProgress 27217603 - can't 
> shrink relation
> WARNING:  Rel pg_attribute: TID 152/1: InsertTransactionInProgress 27217603 - 
> can't shrink relation
> WARNING:  Rel pg_attribute: TID 152/2: InsertTransactionInProgress 27217603 - 
> can't shrink relation
> ...
> ...
> And so on.  The source code says "this should never happen".

7.4 has downgraded those messages to NOTICEs, and says

/*
 * This should not happen, since we hold exclusive
 * lock on the relation; shouldn't we raise an error?
 * (Actually, it can happen in system catalogs, since
 * we tend to release write lock before commit there.)
 */

If you saw it on anything besides a system catalog, then I'm interested,
but otherwise not to worry.

BTW, you really should update to 7.3.4.

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html