"Ivetta Starikova" <[EMAIL PROTECTED]> writes:
> I have a problem with my program that inserts records into postgreSQL
> database.
> After continuously running for several days, it suddenly hangs.
Looks to me like it's waiting for the server process. Are you sure
there isn't some other operation
On Thu, Feb 19, 2004 at 07:16:42PM +0100, Alexander Troppmann wrote:
>SELECT SETVAL('recipe_id_seq', max(id)) FROM recipe;
>
> returns the following output:
>
> setval
>
>455
>(1 row)
Ok.
> Now I tried to fetch the next free primary key id for my "recipe" table:
POSTGRESQL BUG REPORT TEMPLATE
Your name : Alexander Troppmann
Your email address : [EMAIL PROTECTED]
Syste
The reason it is a bug rather than an unimplemented feature
is that it pokes a hole in the effectiveness of domains.
What good is a domain if it cannot be enforced everywhere
you use it? That is like having a hole in referential
integrity. (Though I admit not many people will run into
this until
plpgsql should be trying to coerce the return value to the functions return
type:
rms=# create or replace function retval(integer) returns text as ' begin
return $1::integer; end; ' language 'plpgsql';
CREATE FUNCTION
rms=# select retval(1) || ' is text';
?column?
---
1 is text
(1 row
I'm coming from a Pro*C background so I'm not entirely
certain whether what I am attempting is simply not
allowed in ecpg or not.
ecpg --version
ecpg (PostgreSQL 7.4.1) 3.1.0
showbug.pgc
--
#define HOSTSIZE 100
exec sql begin declare section;
typedef stru
Title: Message
Hi,
I am trying to
restore data from a production server (using Postgresql 7.3.x) to a test server
using the latest release 7.4.1.
This is what I
did:
1) dropdb -U
postgres testdb
2) createdb -U
postgres testdb
3) pg_restore -U
postgres -O -d testdb data.tar
It throws this
