Skip site navigation (1) Skip section navigation (2)

Re: plpython crash on exception

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Postgres Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: plpython crash on exception
Date: 2007-11-23 08:53:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On 11/23/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Marko Kreen" <markokr(at)gmail(dot)com> writes:
> > On 11/23/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Why?  I can't imagine any real use for it.  If you're thinking that
> >> it could provide a guide as to what to resize the buffer to, think
> >> again.
> >  If the output was truncated due to this limit then the return
> >  value is the number of characters (not including the trailing
> >  '\0') which would have been written to the final string if
> >  enough space had  been  available.
> > What problem do you see?
> The problem is that you are quoting from some particular system's
> manual, and not any kind of standard ... much less any standard that
> every platform we support follows.
> The real-world situation is that we are lucky to be able to tell
> vsnprintf success from failure at all :-(

Ah, ok.

I just saw the result used inside the function, so I thought
it is standard enough.

Actually, the meaning could be changed to *needmore
and compensated inside function:

 *needmore = (nprinted < buf->maxlen) ? buf->maxlen : nprinted + 1;

Then it would not matter if libc is conforming or not.


In response to


pgsql-patches by date

Next:From: Marko KreenDate: 2007-11-23 09:55:22
Subject: Cleaner API for appendStringInfoVA
Previous:From: Tom LaneDate: 2007-11-23 07:46:36
Subject: Re: plpython crash on exception

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group