Re: [HACKERS] Dyamic updates of NEW with pl/pgsql

2010-03-16 Thread Merlin Moncure
On Tue, Mar 16, 2010 at 5:53 PM, Florian Pflug wrote: > which returns the field named from the record. The expected > field type is specified by providing a default value in of the > expected type. Since that argument's type is ANYELEMENT, just like the > return type, the type system copes perfe

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Hitoshi Harada
2010/3/17 Tom Lane : > Gokulakannan Somasundaram writes: >>> transformSortClause is passed the untransformed aggorder list, which is >>> in fact a list of SortBy nodes, and it returns the transformed list >>> (SortGroupClause nodes), which is stored back into the aggorder field >>> a bit further d

Re: [HACKERS] Streaming replication, and walsender during recovery

2010-03-16 Thread Fujii Masao
On Tue, Mar 16, 2010 at 6:11 PM, Heikki Linnakangas wrote: > Commmitted. I edited the message and error code a bit: > > ereport(FATAL, >        (errcode(ERRCODE_CANNOT_CONNECT_NOW), >         errmsg("recovery is still in progress, can't accept WAL > streaming connections"))); > > ERRCODE_CANNOT_CO

Re: [HACKERS] Dyamic updates of NEW with pl/pgsql

2010-03-16 Thread Florian Pflug
On 13.03.10 18:38 , Tom Lane wrote: I wrote: ... Maybe it would work to devise a notation that allows fetching or storing a field that has a runtime-determined name, but prespecifies the field type. Actually only the "fetch" end of it is an issue, since when storing the field datatype can be inf

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Tom Lane
Gokulakannan Somasundaram writes: >> transformSortClause is passed the untransformed aggorder list, which is >> in fact a list of SortBy nodes, and it returns the transformed list >> (SortGroupClause nodes), which is stored back into the aggorder field >> a bit further down. > Right Tom. I got c

Re: [HACKERS] parametrized NOTIFY - issue in plpgsql, maybe ToDo

2010-03-16 Thread Pavel Stehule
2010/3/16 Tom Lane : > Pavel Stehule writes: >> I am testing NOTIFY statement. It have to be used from plpgsql via >> EXECUTE, because doesn't support paramaters. > >> Can be it documented somewhere? > > It is.  Use the function instead. ok thank you for info Pavel > >                        reg

Re: [HACKERS] parametrized NOTIFY - issue in plpgsql, maybe ToDo

2010-03-16 Thread Tom Lane
Pavel Stehule writes: > I am testing NOTIFY statement. It have to be used from plpgsql via > EXECUTE, because doesn't support paramaters. > Can be it documented somewhere? It is. Use the function instead. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql

[HACKERS] parametrized NOTIFY - issue in plpgsql, maybe ToDo

2010-03-16 Thread Pavel Stehule
Hello I am testing NOTIFY statement. It have to be used from plpgsql via EXECUTE, because doesn't support paramaters. Can be it documented somewhere? create or replace function foo(a varchar) returns void as $$ begin execute 'notify xxx, ' || quote_literal(a); return; end; $$ language plpgsq

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Gokulakannan Somasundaram
> > transformSortClause is passed the untransformed aggorder list, which is > in fact a list of SortBy nodes, and it returns the transformed list > (SortGroupClause nodes), which is stored back into the aggorder field > a bit further down. > > There are a number of regression tests that would fail

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Tom Lane
Gokulakannan Somasundaram writes: >I noticed a problem with the source code of 9.0Alpha 4. In parse_agg.c, > there is a call made to transformSortClause. > ... >Here agg->aggorder should be a List of SortGroupClause pointers, whereas > transformSortClause expects the second argument as a l

Re: [HACKERS] [RFC] Comments on PostPic project - Repost

2010-03-16 Thread Domenico Rotiroti
Albe Laurenz wrote: > There's the "vacuumlo" contrib module that removes orphaned > large objects. > > Thanks for pointing out. Vacuumlo looks at oid and lo columns to find orphaned lobs, but the idea could be easily adapted/extended to looks for image columns. > Why don't you use bytea instead

Re: [HACKERS] An idle thought

2010-03-16 Thread Tom Lane
Greg Stark writes: > However then I started thinking about this case and wondered if it > wouldn't be possible to optimize. One of the suggested optimizations > was to look at using TRUNCATE. But I wonder why it's necessary to use > a dedicated command. Shouldn't it be possible for the system to n

[HACKERS] An idle thought

2010-03-16 Thread Greg Stark
A few days ago there was a thread on one of our lists where someone was suprised it took as much i/o to delete data as it took to insert it in the first place. At first this does seem surprising but the fact that Postgres stores its transaction information inline with the data and does all i/o in b

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Alvaro Herrera
Gokulakannan Somasundaram escribió: > Hi, >I noticed a problem with the source code of 9.0Alpha 4. In parse_agg.c, > there is a call made to transformSortClause. > > 00098 torder = transformSortClause > (

Re: [HACKERS] [RFC] Comments on PostPic project - Repost

2010-03-16 Thread Domenico Rotiroti
Albe Laurenz wrote: > There's the "vacuumlo" contrib module that removes orphaned > large objects. > > Thanks for pointing out. Vacuumlo looks at oid and lo columns to find orphaned lobs, but the idea could be easily adapted/extended to looks for image columns. > Why don't you use bytea instea

Re: [HACKERS] [RFC] Comments on PostPic project - Repost

2010-03-16 Thread Domenico Rotiroti
On Tue, Mar 16, 2010 at 1:04 PM, Albe Laurenz wrote: > Domenico Rotiroti wrote: > > I would like to receive comments/suggestions about this > > project: http://github.com/drotiro/postpic. > > > > In short, it's an extension that enables image processing > > within the database, adding a new type (

Re: [HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Gokulakannan Somasundaram
Hi, I think, this should be the probable fix. There is agg_order in ParseFuncOrColumn, which should get passed on to transformAggregateCall and that should be placed in this call, instead of agg->aggorder. Thanks, Gokul. On Tue, Mar 16, 2010 at 5:19 PM, Gokulakannan Somasundaram < gokul...@g

Re: [HACKERS] [RFC] Comments on PostPic project - Repost

2010-03-16 Thread Albe Laurenz
Domenico Rotiroti wrote: > I would like to receive comments/suggestions about this > project: http://github.com/drotiro/postpic. > > In short, it's an extension that enables image processing > within the database, adding a new type (image) and several functions. > > The image is represented by

[HACKERS] Bug in 9.0Alpha4

2010-03-16 Thread Gokulakannan Somasundaram
Hi, I noticed a problem with the source code of 9.0Alpha 4. In parse_agg.c, there is a call made to transformSortClause. 00098 torder = transformSortClause (pstate, 00099 a

Re: [HACKERS] Streaming replication, and walsender during recovery

2010-03-16 Thread Heikki Linnakangas
Fujii Masao wrote: > On Mon, Jan 18, 2010 at 2:19 PM, Fujii Masao wrote: >> When I configured a cascaded standby (i.e, made the additional >> standby server connect to the standby), I got the following >> errors, and a cascaded standby didn't start replication. >> >> ERROR: timeline 0 of the pri

Re: [HACKERS] Getting to beta1

2010-03-16 Thread Dimitri Fontaine
Josh Berkus writes: > Yes, and on pgsql-docs rather than on this mailing list. > > Or ... J.F.D.I (Just F Do It). That is, if someone contributed a > whole buncha new text to the tutorial on pgsql-docs, I can't imagine it > being rejected out of hand. That was the bulk of the question, thank

[HACKERS] [RFC] Comments on PostPic project - Repost

2010-03-16 Thread Domenico Rotiroti
I had no answer from pgsql-general, so I'm reposting here. Hello, I would like to receive comments/suggestions about this project: http://github.com/drotiro/postpic. In short, it's an extension that enables image processing within the database, adding a new type (image) and several functions. The