Re: [BUGS] Intermittent Regression test failure in create_misc

Robert Hentosh ([EMAIL PROTECTED]) writes: > Postgresql was compiled with ./configure --enable-syslog after > modifying "#define BLCKSZ 16384" in src/include/config.h.in Hm. I wonder if that is triggering the problem, or if it's something platform-dependent? Could you rebuild with standard bloc

Re: [BUGS] pg_dump Segmentation fault(core dumped)

Hello > pg_dump -o mydb > ... > What it means, and how realy dump database. To dump: pg_dump -o mydb > dump_file To restore: createdb mydb psql mydb

[BUGS] Intermittent Regression test failure in create_misc

Robert Hentosh ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description Intermittent Regression test failure in create_misc Long Description After fetching the latest CVS yesterday. I ran the regression test several times in a row. Act

[BUGS] pg_dump Segmentation fault(core dumped)

Hi All, pg_dump -o mydb CREATE TABLE pgdump_oid (dummy int4); COPY pgdump_oid WITH OIDS FROM stdin; 199150660 \. DROP TABLE pgdump_oid; PQgetvalue: ERROR! tuple number 0 is out of range 0..-1 Segmentation fault(core dumped) What it means, and how realy dump database. -- Vadim I. Pass

Re: [BUGS] Strangeness/bug when working with my own datatype in P ostgreSQL

=?KOI8-R?Q?=F3=CF=CC=CF=C4=CF=D7=CE=C9=CB=CF=D7_=EB=CF=CE=D3=D4=C1?= =?KOI8-R?Q?=CE=D4=C9=CE?= <[EMAIL PROTECTED]> writes: > create type int1 ( input = int1_in, output = int1_out, internallength = 1, > externallength = 3, default = "" ); I'm not sure what it will do to specify a default value fo

[BUGS] COPY doesn't works with es_ES characters

I finally percated that when data contains 'ñ' or 'à' it's impossible to parse trought: COPY products FROM '/var/lib/postgres/dadesi.txt' USING DELIMITERS '|' \g it causes: SELECT edicion FROM products; edicion - España|Nacional <---puts on the same cell either th

[BUGS] The driver told me to do it.

Hi. As per the instructions in the exception message, I report this bug. However, this my first encounter with JDBC, so I'm pretty sure this is because of some newbie mistake on my part. If indeed this is the case, please feel free to enlighten me. The postgresql jdbc driver gave me this error

Re: Lock Detection (was: [BUGS] pg_dump failing on LinuxPPC)

Tom Lane wrote: > > Stu Coates <[EMAIL PROTECTED]> writes: > > I come from an Oracle background where I can lock an item of data by > > performing a "SELECT FOR UPDATE" on the row. This is also implemented > > in PostgreSQL. A quite useful feature Oracle does have is the ability > > to add a "N

[BUGS] psql v. postmaster

PostgreSQL 7.0.3 SunOS amber 5.8 Generic_108529-05 i86pc i386 i86pc gcc version 2.95.2 19991024 (release) configure --with-perl --enable-syslog --with-locale --with-odbc postmaster -S -i -D su - psql Password: psql: pqReadData() -- backend closed the channel un

[BUGS] JDBC packaging error in 7.0.3 with RPM

Patrice Le Gurun ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description JDBC packaging error in 7.0.3 with RPM Long Description I had recently a bug in my Java application. I got a ResultSet from a request to the DB and I had to go t

Lock Detection (was: [BUGS] pg_dump failing on LinuxPPC)

Tom Lane wrote: > > Stu Coates <[EMAIL PROTECTED]> writes: > > Anyway, I've sorted my obsolete version problem, and have discovered > > another. Attached is a short shell script that causes pg_dump to core > > dump whilst trying to dump a single, quite simple, table. > > Fix committed --- but i

RE: [BUGS] Strangeness/bug when working with my own datatype in PostgreSQL

Hello, Tom. I tried to reproduce the situation from the very beginning (created a new DB, created the datatype in it) but the effect did not reproduce. I continued the investigation and found that it is just suffictient to re-create a datatype in an existing DB for the effect to disappear. Thus,