Robert Haas writes:
> On Sat, Sep 19, 2009 at 3:53 PM, Tom Lane wrote:
>> "Tim Bunce" writes:
>>> The plperl implementation doesn't call perl_destruct() during server
>>> shutdown.
>>
>> Who cares? The process is going away anyway.
> END {} blocks can execute arbitrary code. Perl users will
On Sat, Sep 19, 2009 at 3:53 PM, Tom Lane wrote:
> "Tim Bunce" writes:
>> The plperl implementation doesn't call perl_destruct() during server
>> shutdown.
>
> Who cares? The process is going away anyway.
END {} blocks can execute arbitrary code. Perl users will expect them
to be executed.
..
The following bug has been logged online:
Bug reference: 5068
Logged by: Paulo
Email address: correio@gmail.com
PostgreSQL version: 8.4
Operating system: win2003
Description:LIKE
Details:
like to select a field containing Numeric 4 and compared with a char(30)
f
"Pasquale" writes:
> I don't connect any more to postres db because postgres needs to vacuum
> operation.
> Then, i use a standalone backend to connect to postgres db.
> Now i'm im in backend> and i write VACUUM FULL.
You don't really need VACUUM FULL, only VACUUM.
> I have this message:
> WARN
Tomas Psika writes:
> when primary key or unique index is created using explicit name, strange
> notice will say that implicit name was generated. But it didnt.
> # alter table dummy add constraint pk_dummy_x primary key (x);
> NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
> "
The following bug has been logged online:
Bug reference: 5067
Logged by: Pasquale
Email address: pasquale.napolit...@gmail.com
PostgreSQL version: 8.1
Operating system: Linux Red HAT
Description:vacuum problem
Details:
I have this problem:
I don't connect any more t
Hi,
when primary key or unique index is created using explicit name, strange
notice will say that implicit name was generated. But it didnt.
# select version();
PostgreSQL 8.4.1 on i686-pc-linux-gnu, compiled by GCC
i686-pc-linux-gnu-gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4, 32-bit
# create tab
"Tim Bunce" writes:
> The plperl implementation doesn't call perl_destruct() during server
> shutdown.
Who cares? The process is going away anyway.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
h
The following bug has been logged online:
Bug reference: 5066
Logged by: Tim Bunce
Email address: tim.bu...@pobox.com
PostgreSQL version: 8.4.1
Operating system: darwin
Description:plperl issues with perl_destruct() and END blocks
Details:
The plperl implementation
