Also another bug and usecase connected with subj.
It creates parent table "xtest", inherited table "xtest_inh" with
some data, and a trigger BEFORE INSERT/UPDATE/DELETE on table "xtest".
After, it deletes one row.
**
CREATE TABLE xtest (id serial, data varchar, prim
Ok, thanks, roger you.
But one question still cause my misunderstanding:
> > 2. If i create trigger FOR EACH STATEMENT, it will work ok for
> > insert, update and delete.
>
> You mean FOR EACH ROW, no?
Yes, confused. FOR EACH ROW.
"FOR EACH ROW"-trigger successfully fires in inherited
table "xte
Jorge Augusto Meira escreveu:
> This is a bug?
>
You don't provide sufficient information. PostgreSQL version? Error message?
Talking about your problem, are you sure you're not reaching max_connections?
Did you check the logs?
--
Euler Taveira de Oliveira
http://www.timbira.com/
--
Sent
Euler Taveira de Oliveira wrote:
> Talking about your problem, are you sure you're not reaching
> max_connections?
It also strikes me that from the minimal information given, it might
be possible that pid numbers or port numbers are wrapping around
before the OS is ready to allow re-use. I h
Hi, the link on the page http://www.postgresql.org/about/news.142 is not
working.. I tried to download this old release in order to test something
and could not.
Best regards, Hanna.
On 03.12.2010 12:43, Балукова Анна wrote:
Hi, the link on the page http://www.postgresql.org/about/news.142 is not
working.. I tried to download this old release in order to test something
and could not.
Older releases are available at ftp://ftp-archives.postgresql.org
--
Heikki Linnakangas
Konstantin Nikiforov writes:
> Also another bug and usecase connected with subj.
> It creates parent table "xtest", inherited table "xtest_inh" with
> some data, and a trigger BEFORE INSERT/UPDATE/DELETE on table "xtest".
> After, it deletes one row.
I think you fundamentally misunderstand how tr
I have discovered either a bug in pgcrypto (postgresql-9.0.1) or at least an
implementation change that is incompatible with how I've been using pgcrypto.
I'm hoping a discussion here on bugs@ is an appropriate first course of
discussion.
I have a couple of databases in which I have been using
On 03.12.2010 19:48, daniel wrote:
I have discovered either a bug in pgcrypto (postgresql-9.0.1) or at least an
implementation change that is incompatible with how I've been using pgcrypto.
I'm hoping a discussion here on bugs@ is an appropriate first course of
discussion.
I have a couple of
The following bug has been logged online:
Bug reference: 5782
Logged by: Alexia Lau
Email address: a...@esri.com
PostgreSQL version: 9.0.1 64-bit
Operating system: Windows 2008 R2 64-bit
Description:No UUID support with one-click installer PostgreSQL
9.0.1 64-bit for
I have installed PostgreSQL 9.0.1 64-bit Windows one-click installer from
EnterpriseDB and noticed that there is no uuid-ossp.dll and uuid-ossp.sql
available. With PostgreSQL 9.0.1 32-bit Windows one-click installer this is
avaialable.
I found a link below below from a user who indicated that OS
On Dec 3, 2010, at 1:49 PM, Heikki Linnakangas wrote:
> On 03.12.2010 19:48, daniel wrote:
>> I have discovered either a bug in pgcrypto (postgresql-9.0.1) or at least an
>> implementation change that is incompatible with how I've been using
>> pgcrypto. I'm hoping a discussion here on bugs@ is
12 matches
Mail list logo
