> I get the feeling that what we will see is the destination
> filename already present and the source not, which would suggest
> that two backends tried to do the rename concurrently.
Tom,
I just noticed that the rename panic errors like this one:
PANIC: rename from /data/pg_xlog/00030
Cygwin, 7.3.4
This thing is really KILLING us and our customers.
In pgerr.log this always go together:
WARNING: ShmemAlloc: out of memory
ERROR: FreeSpaceMap hashtable out of memory
Theses errors usually take place on INSERT statements like this one:
INSERT INTO params (param_id,map_id,param_
9:37 AM
To: Yurgis Baykshtis
Cc: PostGreSQL mailing list
Subject: Re: [HACKERS] PostgreSQL and Windows
Yurgis Baykshtis wrote:
>
> We have a similar question about upcoming Windows "native" release:
>
> Is it going to be multithreaded or one process per connection like on
&g
We have a similar question about upcoming Windows "native" release:
Is it going to be multithreaded or one process per connection like on
cygwin?
-Original Message-
From: P.M [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 11:10 PM
To: PostGreSQL mailing list
Subject: [HACKERS
The problem happens only when running this query from the plpgsql
function... So it must be a bug specific to plpgsql parser.
-Original Message-
From: Yurgis Baykshtis
Sent: Wednesday, May 28, 2003 1:07 PM
To: [EMAIL PROTECTED]
Subject: Mismatched parentheses when creating a rule with
PostgreSQL 7.3.2.
The parser does not seem to like semicolon between action queries:
(Mismatched parentheses)
So, it makes impossible to create a rule with more than one action
query.
Or am I missing something?
CREATE RULE my_insert_rule AS ON INSERT
TO my_view
DO INSTEAD
(
INSERT IN
