Hai,
I'm using postgresql 7.2
There is a bug in pg_restore. It is not restoring the sequences
properly. and it is failing with views created by pgadmin tool.
It is restoring , but giving the following error with sequences
and
recovery is failing
Archiver(db): Could not execute query. Code = 7. E
Using the JDBC interface to inspect the metadata in a table, the
ResultSet returned from using DatabaseMetaData.getImportedKeys
includes values for KEY_SEQ. This is an integer value and in the
case of Postgreql starts at zero.
I can find no formal definition of where this value should start
but
Hello,
I discovered a bug in the connect statements of postgresql 7.2. After a
pg_dumpall in postgresql 7.1.3, upgrading to Postgresql 7.2 and an
initdb, the following lines from the script, generated by pg_dumpall,
cause a problem:
---
\connect template1 postgres
CREATE DATABASE "iBBS-oud" WITH
Hi,
trying to import an ascii file with the sql copy statement
fails in the pg_atoi routine
if the last field is "int"
and
if the ascii file has DOS line endings (cr=0x0d and lf=0x0a).
The main problem is the error message: you cannot detect
the cr on the screen, you see only a "unknown" e
create table ref_table (
id serial primary key
ref_name varchar);
create table data_table (
a int4 references ref_table);
which of course creates 3 triggers.
If you do:
alter table data_table rename column a to b;
The trigger on data_table still looks for column named "a" so sometime in
After running the postmaster, and after the command
inidtb has been done successfully, when I try to use
the commands createdb or psql in postgresql, I get the
following message:
FATAL 1: Database system does not exist. PGDATA
directory `/usr/local/pgsql/data` not found.
Normally, you create
Hello,
I have just installed Postgresql 7.1 on an RS6000-F40 from binaries downloaded from
Bull. The install was flawless. I however cannot get past the need to create a
database as psql fails as follows:
exec(): 0509-036 Cannot load program psql because of the following errors:
0509-15
When I run the configure script I'm getting this error:
checking for optreset... no
checking test program... failed
configure: error:
*** Could not execute a simple test program. This may be a problem
*** related to locating shared libraries. Check the file 'config.log'
*** for the exact reas
I have used server version of the perl modules DBD::Pg and Pg. I have
looked over the modules and the DBI package and believe the problem
might be with the libq.
When you pass a oid to the lo_open it doesn't seem to be able to accept
it and cause and error to be generated in the log file: ERROR:
Srinivasa R Chava <[EMAIL PROTECTED]> writes:
> I'm using postgresql 7.2
> There is a bug in pg_restore. It is not restoring the sequences
> properly. and it is failing with views created by pgadmin tool.
This is not a bug in pg_restore, but in pg_dump: it's emitting the
stuff in the wrong order.
I created a temporary table using a procedure called from VB. The
table contains int8 and text data. I display the data contained in the
temporary table using a datagrid with the datasource set to a recordset that is
opened through code (no data control or data environment used). The
prob
POSTGRESQL BUG REPORT TEMPLATE
Your name : Alain Picard
Your email address : [EMAIL PR
The contrib rpm for postgresql 7.2 doesnt seem to work correctly for me.
I am trying to install pgcrypt module, but it is looking for
'$libdir/pgcrypto'. I assume that this should be translated to the
actual compiled C lib. Let me know if nobody wants to or has the time to
fix this.
Thanks,
Greg
Hello,
I have downloaded postgresql 7.2 on my machine.
Running ecpg on my .ec-file I found that ecpg did not process
the statements "exec sql declare xxx cursor for select.
The part in my .ec-file:
if ( firstcall )
{
calid1 = calid;
EXEC SQL DECLARE CURMFDPOINT CURSOR FOR SELECT STABLE
Torres Abarca Jaime <[EMAIL PROTECTED]> writes:
> When I run the configure script I'm getting this error:
See item 3 in doc/FAQ_Solaris.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, p
A little more info ... it fails on any file ... I tested with a 1 byte
file with a single byte (value of that byte is irrespective ... fails in
all cases)
Original Message
java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340...
I'm on Linux 2.4.16 using J
(NOTE: This is a report ... my cut-and-paste went a little haywire on
the last one.)
BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver
though. Basically, returns an error like the following on executeUpdate():
java.sql.SQLException: ERROR: oidin: error in "x": can
POSTGRESQL BUG REPORT TEMPLATE
Your name : Eugene Pervago
Your email address : [EMAIL PROTECT
"Chuck Handshy" <[EMAIL PROTECTED]> writes:
> When you pass a oid to the lo_open it doesn't seem to be able to accept
> it and cause and error to be generated in the log file: ERROR:
> lo_lseek: invalid large obj descriptor (0) <- Note descriptor (0), I
> passed 16832 to it as the oid.
Descriptor
Alain Picard <[EMAIL PROTECTED]> writes:
> Behold!
> select * from test_table
> where data !=''
> and
> data != '';
> -> returns:
>id |
Eugene Pervago <[EMAIL PROTECTED]> writes:
> 1. select cash_words('21,474,836.48'::money);
> 2. Crashes.
Fixed for 7.2.1. Thanks for the report!
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list
Denis Medvedev ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
bind to 127.0.0.1 in pgstat.c in secure server
Long Description
I am trying to run postgresql in secure server where is
only one IP available.
There is no means to
Thanks to Tom Lane and to Jan-Benedict Glaw for suggesting
a RAM problem; this has now been confirmed.
I'm relieved that Postgresql does not have what would have
been a very fundamental problem. That's the first time I
find a "bug" which is actually a hardware fault. I guess
sometimes the com
Craig Brown ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
ResultSet.next() throws NullPointerException
Long Description
When invoking the next() method on a ResultSet that has been closed a
NullPointerException is thrown. I
24 matches
Mail list logo
