Mark Shewmaker <[EMAIL PROTECTED]> writes:
> If a "FOR UPDATE executes before LIMIT" rule stopped the function
> from ever locking a row, it's still curious why didn't it stop the
> direct command from ever locking a row as well.
I think it would. Did you try the test the other way ar
On Wed, 2003-12-17 at 14:02, Tom Lane wrote:
> Mark Shewmaker <[EMAIL PROTECTED]> writes:
> > In other words: Is this a bug or a user misunderstanding:
>
> You've got the function doing
>
> > LOOP
> > select * into myrow from mytable limit 1 for update;
> > if found then exit;
>
The following bug has been logged online:
Bug reference: 1012
Logged by: Böjthe Zoltán
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux Suse 9.0
Description:missing server/*.h on suse devel rpm package
Details:
the /usr/include/pgsql/
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> There is test case (notice there is ltree column):
Seems to be a buffer overrun in lquery_out(). I've applied the attached
patch for 7.4.1.
regards, tom lane
*** contrib/ltree/ltree_io.c.orig Sun Aug 3 20:43:10
Mark Shewmaker <[EMAIL PROTECTED]> writes:
> In other words: Is this a bug or a user misunderstanding:
You've got the function doing
> LOOP
> select * into myrow from mytable limit 1 for update;
> if found then exit;
> end if;
> END LOOP;
which means it will loop infin
tim <[EMAIL PROTECTED]> writes:
> I've found a minor bug whilst using psqlodbc to connect to PostgreSQL. I have
> found that if you set in postgresql.conf:
> client_min_messages=log
> log_duration=true
> you are unable to connect to any db using the psqlodbc driver.
Hm. This sounds like psql
Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > When a client connects to the database server using a service name,
> > the dbname parameter in pg_service.conf is ignored. In the absence
> > of an explicitly-named database in the connection string, the service
> > name is used as th
Michael Fuhr <[EMAIL PROTECTED]> writes:
> When a client connects to the database server using a service name,
> the dbname parameter in pg_service.conf is ignored. In the absence
> of an explicitly-named database in the connection string, the service
> name is used as the database name regardless
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> The errors are similar to:
> "psql:daily_update.sql:332: ERROR: could not open segment 1 of relation
> "summ_stubcount" (target block 3538944): No such file or directory"
> Note that summ_stubcount is an index.
This appears to indicate corrupt
Should there be a difference between the behavior of a "select for
update" typed into psql directly versus "select into variable_name for
update" done within a function?
In other words: Is this a bug or a user misunderstanding:
1. Run the following commands to set up a table called
mytable
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> head=# select pg_catalog.format_type(oid, typlen) from pg_type where typname =
> 'interval';
> ERROR: invalid INTERVAL typmod: 0xc
This is not a bug. format_type's second arg is typmod, not typlen.
regards, tom lane
11 matches
Mail list logo
