Thank's a lot
with Activestate 64 bit perl 5.10 it works.
It would be very desirable for plperl supporter to to add some plperl release
notes with Postgresql
production release for users to know , with what PERL distribution it works.
Rene Novotny
>>> Alex Hunsaker 5.8.2010 17:33 >>>
On Th
Hello,
I found something weird in the logs.
Apparently the automated analyze process has some
problems with custom functions.
Using my regular database user for this db, i get no problems
using the functions which fail for the automated analyze process.
Can this be a sear
The following bug has been logged online:
Bug reference: 5608
Logged by: Itagaki Takahiro
Email address: itagaki.takah...@gmail.com
PostgreSQL version: 9.0beta4
Operating system: Windows 7 (32bit)
Description:array_agg() consumes too much memory
Details:
I encounter
postgres=# CREATE OR REPLACE FUNCTION f_test() RETURNS VOID AS $$
DECLARE
arr text[];
lr text;
i integer;
BEGIN
i := 1;
SELECT 'foo' INTO lr;
arr[COALESCE(i, (SELECT NULL::integer))] := COALESCE(lr, (SELECT
NULL::text));
END;
$$ LANGUAGE PLPGSQL;
CREATE FUNCTION
postg
Hi,
I'm using libpq PQexecParams ability to send query parameters as binary data,
more specific - a binary representation of an empty array.
I have the problem:
the code sending empty binary array works on 8.3 and 8.4
but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','intege
writes:
> I have the problem:
> the code sending empty binary array works on 8.3 and 8.4
> but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','integer
> out of range error'.
I think you are right --- this rejects dim[i] == 0, but it should not.
regard
Heikki Linnakangas writes:
> TRAP: FailedAssertion("!(estate->eval_tuptable == ((void *)0))", File:
> "pl_exec.c", Line: 4264)
> This happens when both the array subscript and the expression been
> assigned are "non-simple". The purpose of the funny-looking COALESCE
> expressions in the above
I wrote:
> Yeah, I don't like that either. What we need to do instead is fix
> exec_assign_value so that it can cope with the case of the caller having
> an open expression evaluation. We can easily have it save/restore
> eval_tuptable. Not resetting eval_econtext is a bit harder, but maybe
> we
On 09/08/10 19:32, Tom Lane wrote:
I wrote:
Yeah, I don't like that either. What we need to do instead is fix
exec_assign_value so that it can cope with the case of the caller having
an open expression evaluation. We can easily have it save/restore
eval_tuptable. Not resetting eval_econtext i
Heikki Linnakangas writes:
> There's a related issue:
> ...
> This one is simple to fix, we can always call exec_eval_cleanup() before
> running the exception handler:
Sounds good, will add that and some regression tests and commit.
regards, tom lane
--
Sent via pgsql-
On 09/08/10 17:56, Tom Lane wrote:
writes:
I have the problem:
the code sending empty binary array works on 8.3 and 8.4
but stopped working on postgres 9.0 beta2/3/4, it fails with '22003','integer
out of range error'.
I think you are right --- this rejects dim[i] == 0, but it should not.
Heikki Linnakangas writes:
> The behavior of empty arrays with dimensions is weird in general.
Agreed, but we shouldn't be introducing random restrictions in the name
of security.
Patch looks good to me, except that it occurs to me to wonder about
negative values of dim[i]. For small negative v
On 09/08/10 21:26, Tom Lane wrote:
Heikki Linnakangas writes:
The behavior of empty arrays with dimensions is weird in general.
Agreed, but we shouldn't be introducing random restrictions in the name
of security.
Patch looks good to me, except that it occurs to me to wonder about
negative va
The following bug has been logged online:
Bug reference: 5609
Logged by: Rob Brucks
Email address: rob.bru...@rackspace.com
PostgreSQL version: 8.3.7
Operating system: Ubuntu 8.04
Description:Exclusive Locks & Permission
Details:
If a user that does not have permiss
On Sun, Aug 1, 2010 at 3:39 PM, Mike Parfitt wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5587
> Logged by: Mike Parfitt
> Email address: m_parf...@hotmail.com
> PostgreSQL version: 8.4.4.1
> Operating system: Windows XP SP3
> Description: Ins
"Rob Brucks" writes:
> The user's permissions need to be checked before requesting an exclusive
> lock on the table for the alter.
Unfortunately, that cure is as bad or worse than the disease. It's not
possible to do a permissions check before acquiring any lock --- what if
somebody is changing
Sorry about that, I hit the submit button on accident before I finished typing
out the issue. But I guess there was enough there for you to understand the
problem.
Thanks for the quick response.
Is there any alternative I can use to prevent the exclusive lock (other than
changing the app, we
Rob Brucks writes:
> Is there any alternative I can use to prevent the exclusive lock (other than
> changing the app, we don't have access to the source code)?
Not directly. You might be able to do something with hiding the tables
in schemas that the unprivileged user hasn't got USAGE rights on
On Thu, Aug 5, 2010 at 2:46 PM, Nacho Mezzadra wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5603
> Logged by: Nacho Mezzadra
> Email address: nachomezza...@gmail.com
> PostgreSQL version: 8.3.11
> Operating system: Red Hat Enterprise 5.3
> Descriptio
"Itagaki Takahiro" writes:
> I encountered "out of memory" error in large
> GROUP BY query with array_agg(). The server log
> was filled by the following messages:
> accumArrayResult: 8192 total in 1 blocks; 7800 free (0 chunks); 392
> used
> Should we choose smaller size of initial memory i
Severity: Minor
Version tested: 8.4.4
Platform: Solaris 10u8
Steps to reproduce:
1. Create table "sometable" owned by user "someuser", and fill it with a
million generate_series records.
2. Log in as the superuser "postgres".
3. Do:
alter table sometable add column someserial serial;
4. Postgr
Robert Haas writes:
> On Thu, Aug 5, 2010 at 2:46 PM, Nacho Mezzadra
> wrote:
>> PostgreSQL version: 8.3.11
>> Operating system: Red Hat Enterprise 5.3
>> Description: pg_tblspc and pg_twoface directories get deleted when
>> starting up service
> This is pretty scary, but it's a little
22 matches
Mail list logo
