Re: [BUGS] Problem cocatenating String (||)

2004-09-13 Thread Tom Lane
"Thomas Niemeier" <[EMAIL PROTECTED]> writes: > I've got a problem concatenating two fields (char(10) not null) in a select > statement. Let's say the first field pname has the value > 'USER ' and the second field pfirst the value 'JOE '. Then a "select > pname||pfirst from table" would

Re: [BUGS] PosgreSQL is crashing with a signal 11 - Bug?

2004-09-13 Thread Tom Lane
Rafael Martinez Guerrero <[EMAIL PROTECTED]> writes: > To me this looks like a cache somewhere that upon read contained some > incorrect data. This cache was somehow flushed two-hours later, and > fresh data was read from disk. Very possible. > Could this be postgres problem, or is it hardware/k

[BUGS] Problem cocatenating String (||)

2004-09-13 Thread Thomas Niemeier
Hello everybody! I've got a problem concatenating two fields (char(10) not null) in a select statement. Let's say the first field pname has the value 'USER ' and the second field pfirst the value 'JOE '. Then a "select pname||pfirst from table" would return the value 'USERJOE', trimmin

[BUGS] table and column name

2004-09-13 Thread wisan watcharinporn
i think it not bug but it not correct at all i create table with command create table helloWorld () <-- it create table helloworld not helloWorld, i hope it be create helloWorld create table "helloWorld" () <-- ok it create table helloWorld in the same to create column name because in st

[BUGS] BUG #1252: Optimization of SELECT for NOT NULL case

2004-09-13 Thread PostgreSQL Bugs List
The following bug has been logged online: Bug reference: 1252 Logged by: Alexander Kirpa Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: FreeBSD 5.2.1 Description:Optimization of SELECT for NOT NULL case Details: CREATE TABLE x (

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread Tom Lane
elein <[EMAIL PROTECTED]> writes: > I'll verify I have the version I think I have... > (gdb) bt > #0 0x0805dd15 in trim_trailing_separator (path=0x0) at path.c:442 > #1 0x0805d6b2 in canonicalize_path (path=0x0) at path.c:123 > #2 0x0804af80 in exec_command (cmd=0x808f958 "e", scan_state=0x808b

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread elein
This is the source for beta2. Perhap the previous fix was to add the path[0] check but the path == NULL check was forgotten? OR, is it a problem if path==NULL? --elein On Mon, Sep 13, 2004 at 01:31:26PM -0700, elein wrote: > This looks like the same bug as Michael's > http://archives.postgresql

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread elein
This looks like the same bug as Michael's http://archives.postgresql.org/pgsql-bugs/2004-08/msg00103.php trim_directory needs to check for a NULL pointer in path. if ( path == NULL || path[0] == '\0' ) I'll verify I have the version I think I have... (gdb) bt #0 0x0805dd15 in trim_trai

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread Tom Lane
elein <[EMAIL PROTECTED]> writes: > Has anyone else experienced a segfault in psql on 8.0B2 > when using \e? I can reproduce this consistently. Hmm, we fixed a bug in \e not long ago, but it was pre-beta2 ... regards, tom lane ---(end of broadcast

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread Michael Fuhr
On Mon, Sep 13, 2004 at 12:47:54PM -0700, elein wrote: > Has anyone else experienced a segfault in psql on 8.0B2 > when using \e? I can reproduce this consistently. > > If not I'll trace it down if I can, but if it is a known > problem, I won't bother. I'm using the latest CVS sources on Solaris

Re: [BUGS] 8.0B2 psql \e

2004-09-13 Thread Alvaro Herrera
On Mon, Sep 13, 2004 at 12:47:54PM -0700, elein wrote: > Has anyone else experienced a segfault in psql on 8.0B2 > when using \e? I can reproduce this consistently. I do it all the time and I haven't seen it ... is your query too long or something? Care to show psql's backtrace? -- Alvaro Herr

[BUGS] 8.0B2 psql \e

2004-09-13 Thread elein
Has anyone else experienced a segfault in psql on 8.0B2 when using \e? I can reproduce this consistently. If not I'll trace it down if I can, but if it is a known problem, I won't bother. --elein [EMAIL PROTECTED]Varlena, LLC

Re: [BUGS] vacuum problem

2004-09-13 Thread John R Pierce
there are no background programs. I've done all the usual checking of `ps' outputs looking for such. in the test case I mailed to this list, I had created a standalone database with one table, and run the test program directly against it. That sounds suspiciously like you think that only backgr

Re: [BUGS] BUG #1251: setTransactionIsolation does not seem to work

2004-09-13 Thread Kris Jurka
> Bug reference: 1251 > PostgreSQL version: 7.4.3 > Description:setTransactionIsolation does not seem to work > > First of all, the version I am using of PostgreSQL is 7.4.5, and *not* 7.4.3 > (I have set 7.4.3 in the form, since it does not allow to choose 7.4.5). > > I have tes

Re: [BUGS] PosgreSQL is crashing with a signal 11 - Bug?

2004-09-13 Thread Rafael Martinez Guerrero
On Fri, 2004-09-10 at 16:24, Tom Lane wrote: > Kjetil Torgrim Homme <[EMAIL PROTECTED]> writes: > > how can att[i]->attlen possibly change in the interim? but > > data_length looks corrupted, too. > > Unless you compiled with no optimization at all (-O0), the compiler > would likely fold the iden

[BUGS] BUG #1251: setTransactionIsolation does not seem to work

2004-09-13 Thread PostgreSQL Bugs List
The following bug has been logged online: Bug reference: 1251 Logged by: Fernando Bellas Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.3 Operating system: Red Hat 7.1 Description:setTransactionIsolation does not seem to work Details: Hi, First of al

Re: [BUGS] BUG #1233: JDBC driver: moveToCurrentRow fails

2004-09-13 Thread Kris Jurka
> Bug reference: 1233 > Description:JDBC driver: moveToCurrentRow fails > Fixed in 7.4 and 8.0 branches. Thanks for the fix and sorry for the delay, I've been travelling. Kris Jurka ---(end of broadcast)--- TIP 4: Don't 'kill -9'