On Wed, Oct 01, 2003 at 11:38:55PM -0400, Tom Lane wrote:
> Theodore Petrosky <[EMAIL PROTECTED]> writes:
> > I should have sent this... it is very interesting..
> > agencysacks=# select to_timestamp('01 October 2003
> > 00:01', 'DD Month HH24:MI');
> > to_timestamp
> > --
So really if I had started coding this in a month
other than September I would have seen the problem
sooner...
Thanks for the help
Ted
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Theodore Petrosky <[EMAIL PROTECTED]> writes:
> > I should have sent this... it is very
> interesting..
> > agencys
On Wed, Oct 01, 2003 at 07:57:18PM -0700, Theodore Petrosky wrote:
> here is the actual query:
>
> agencysacks=# SELECT jobnumseq, (SELECT cname FROM
> clientinfo ci WHERE ci.acode = j.clientid) as client,
> shrtdesc, to_char(proofduedate, 'Dy FMMon DD,
> HH12 am') FROM jobs j WHERE proof
Hi,
I have found a memory leak in PostgreSQL 7.3.4,
src/interfaces/libpq/fe-exec.c line 279:
buffer = realloc(buffer, buflen);
if (buffer == NULL)
return NULL;
The realloc manpage says:
"If realloc() fails the original block is left untouched - it is
not fre
Karel Zak <[EMAIL PROTECTED]> writes:
> The to_timestamp() do nothing with date/time and use internal
> tm2timestamp() routine only. I don't think that check all date/time
> ranges in to_timestamp() is good idea if it's already implemented at
> the another place in our code.
But it evidently
On Thu, Oct 02, 2003 at 10:04:39AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > The to_timestamp() do nothing with date/time and use internal
> > tm2timestamp() routine only. I don't think that check all date/time
> > ranges in to_timestamp() is good idea if it's already
Max Kellermann <[EMAIL PROTECTED]> writes:
> I have found a memory leak in PostgreSQL 7.3.4,
> src/interfaces/libpq/fe-exec.c line 279:
This appears to have been dealt with already (although realistically,
it would be an extremely brain-dead realloc that could ever fail here,
since the block is be
