From: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stefan Schwarzer <stefan(dot)schwarzer(at)grid(dot)unep(dot)ch> |
Subject: | Re: Crosstab Problems |
Date: | 2007-10-18 23:02:54 |
Message-ID: | 200710182102.56340.jgodoy@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Em Thursday 18 October 2007 16:37:59 Joe Conway escreveu:
> Tom Lane wrote:
> > so it's trying to pstrdup a null result from SPI_getvalue.
> >
> > Obviously it shouldn't crash, but I'm not sure what it *should* do in
> > this case. Joe?
>
> The row is pretty useless without a rowid in this context -- it seems
> like the best thing to do would be to skip those rows entirely. Of
> course you could argue I suppose that it ought to throw an ERROR and
> bail out entirely. Maybe a good compromise would be to skip the row but
> throw a NOTICE?
If I were using it and having this problem I'd rather have an ERROR. It isn't
uncommon for people not look at their logs and it isn't uncommon for them
just run command from some language using a database adapter that might not
return the NOTICE output. The ERROR wouldn't pass unnoticed.
--
Jorge Godoy <jgodoy(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Godoy | 2007-10-18 23:21:16 | Re: running postgres |
Previous Message | brian | 2007-10-18 22:13:23 | Re: Group By question |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-19 03:09:12 | Re: Crosstab Problems |
Previous Message | Heikki Linnakangas | 2007-10-18 21:13:22 | Re: [HACKERS] Why copy_relation_data only use wal whenWALarchivingis enabled |