Re: [BUGS] PostgreSQL memory bug

"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > I use the PostgreSQL 7.4.5 on SLES9.0 and PostgreSQL 7.4.3 on SuSE 9.0 > If you make 'create user' and 'alter group' sql command on existing > users, and make it many times, the server doesn't release the memory. I believe this is the same issue

Re: [BUGS] BUG #1345: pgsql character comparison bug

"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > select > chr(13) Oh! the value of a6 field is "f" !!! Works fine for me. Check your locale setting. regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the

[BUGS] 8.0.0rc1 core dump with PREPARE in a function

PostgreSQL 8.0.0rc1 (CVS HEAD) Solaris 9, FreeBSD 4.11-PRERELEASE I can consistenly produce a core dump by calling a function that executes PREPARE...INSERT or PREPARE...UPDATE, then calling it again. I haven't been able to produce a core dump with PREPARE...SELECT. When I call the function the se

[BUGS] postgresql-8.0.0 beta5 & postgresql-7.4.6 can't compile successfully in Solaris 10 x86

Hi, I tried to build postgresql-8.0.0beta5 and postgresql-7.4.6 on Solaris 10 x86 following the instruction by doing: 1. ./configure 2. gmake When I implemented the step 2. I got the following error messages: --- /usr/local/bin/gcc -O2 -pipe -fno-strict-aliasing -Wall -Wmissing-prototype

[BUGS] concat fails 'sometimes' on empty colums in select

Hi, I have a table with some empty colums, if I try to concat my colums to eachother something strange happens. Rather empty column B produces virtually no output using the || in the select query. But the half filed colum A does give the desired output. midvliet=# select snr, achternaam||', '||

[BUGS] is it bug

Hi when i start this SQL on windows postgres rc1 select fi.ID_PGODINE,fi.ID_OZNAKE_OTPREME,fi.ID_FAKTURE_IZLAZNA,OZN_KP,fi.OZN_VAL_NBJ_STR AS ID_ZEMLJE,ug.ID_UGOVORA, ug.NAP_UGOVORA,fn.TEKST_NAPOMENE,kat.NAZIV_ELEM, CASE fakt_lit WHEN 'Y' THEN 'L' ELSE kat.JM END

Re: [BUGS] 8.0.0rc1 core dump with PREPARE in a function

Michael Fuhr <[EMAIL PROTECTED]> writes: > I can consistenly produce a core dump by calling a function that > executes PREPARE...INSERT or PREPARE...UPDATE, then calling it again. I think this is a variant of the same problem recently detected with DECLARE CURSOR, ie, PREPARE had better copy the s

Re: [BUGS] is it bug

<[EMAIL PROTECTED]> writes: > Hi when i start this SQL on windows postgres rc1 Could we see a self-contained test case for this? The query is useless without tables to run it against. The best way is to provide a SQL script that causes the error when run in an initially-empty database.

Re: [BUGS] concat fails 'sometimes' on empty colums in select

On Sat, Dec 11, 2004 at 03:33:07 +0100, Stefan de Konink <[EMAIL PROTECTED]> wrote: > Hi, > > I have a table with some empty colums, if I try to concat my colums to > eachother something strange happens. Rather empty column B produces > virtually no output using the || in the select query. But

[BUGS] Out of memory problem "More detailed"

Logged by: Lutischan Ferenc Email address: yoursoft ( at ) freemail ( dot ) hu PostgreSQL version: 7.4.3, 7.4.5 Operating system: Linux: SuSE9.0, SLES9 Description:Out of memory Details: Dear Developer Team! I use the PostgreSQL 7.4.5 on SLES9.0 and PostgreSQL 7.4.3 on SuS

[BUGS] create/drop table bug

hello people, my name is Poyo, I'm from a little town near from Buenos Aires -Argentina-  and i'm having problems with the creation/drop of tables from inside of function's. in other words: if you execute the below points in order (1,2,3,4,5) you 'll see this:   ERROR:  relation with OID 176

Re: [BUGS] concat fails 'sometimes' on empty colums in select

On Sat, Dec 11, 2004 at 01:54:35PM -0600, Bruno Wolff III wrote: > > Empty strings and NULL values aren't the same thing. You probably either > want to store empty strings or use coalesce to change NULL to an empty > string before using concatenation, as a NULL concatenated with anything > results

Re: [BUGS] bug at build_dummy_tuple

Alvaro Herrera <[EMAIL PROTECTED]> writes: > This is a weird bug. In a freshly initialized database, or just after > deleting the pg_internal.init relcache file, > SELECT 16854::regclass; > crashes the backend. Ah, I see it. Looks like I was a bit too cute here: http://developer.postgresql.org/c

Re: [BUGS] solaris 10 with gcc 3.3.2

"Belbin, Peter" <[EMAIL PROTECTED]> writes: > Should I be able to compile with gcc 3.3.2 (from sunfreeware) on solaris 10? Yes ... > gcc -DPOSIX -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels > -fno-strict-aliasing -I../../src/port -DFRONTEND -I../../src/include -c -o > exec.o exec.c

Re: [BUGS] pg_autovacuum fails to run as a windows service (beta4)

Just a quick guess, the user account that you are logged in as while attempting to install the service, is it an admin account that has the required privileges? Steve McWilliams wrote: I am unable to run pg_autovacuum as a windows service. I am using 8.0.0beta4 on Windows XP Pro. When I execut

Re: [BUGS] problem while installitn PSQL 8.0 (win)

>While installing both 8.0 beta, 5.o beta and RC1 everything >seems to go ok >until the following stage: Activating procedural languages, when the >installation stops. PostgreSQL server's service initializes >correctly. My OS >is Windows XP SP2. The reason why the situation appears is >that

Re: [BUGS] create/drop table bug

On Fri, Dec 10, 2004 at 05:30:14PM -0300, Libsis wrote: > ERROR: relation with OID 17687 does not exist > CONTEXT: PL/pgSQL function "myfunc" line 5 at for over select rows > > the oid 17687 is corresponding with the table created inside the > function (SELECT INTO newtable) (see point 3) but l