Bruce Momjian <[EMAIL PROTECTED]> writes:
> I am concerned that removing them may cause instability, particularly in
> some of the java build scripts. That's why I am suggesting not doing it
> during beta.
Actually, it looks to me like they belong with the JDBC driver. As long
as JDBC is in the
I notice there's a leak of memory in SPI_prepare().
The full fix is nontrival and I don't want to submit a half solution so I
thought I'd check whether people think it's worth worrying about.
The leak is that memory is grabbed in SPI_prepare() for a plan within whatever
context is current when
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> The leak is that memory is grabbed in SPI_prepare() for a plan within
> whatever context is current when it does the palloc(). It may be the
> caller's or it may be the relevent SPI one. The plan is then copied
> out of this memory [and context] into
On Sat, 19 Oct 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > The leak is that memory is grabbed in SPI_prepare() for a plan within
> > whatever context is current when it does the palloc(). It may be the
> > caller's or it may be the relevent SPI one. The plan is then
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> On Sat, 19 Oct 2002, Tom Lane wrote:
>> I'm not sure where the leak is in your plpython example, but I'd be
>> inclined to look to plpython itself, perhaps even just the string
>> concatenation expression in
>> plan = plpy.prepare("SELECT " + repr(a)
Peter Eisentraut wrote:
Teodor Sigaev writes:
wow=# select 5.3::float;
ERROR: Bad float8 input format '5.3'
Does it accept '5,4'::float?
Yes, it accepted '5,4'::float format.
--
Teodor Sigaev
[EMAIL PROTECTED]
---(end of broadcast)---
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Michael, please use bison 1.75 to update ecpg
Why is this necessary? AFAIK we don't keep bison-derived files in
CVS...
Cheers,
Neil
--
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC
---(end of broadcast)--
Anuradha Ratnaweera <[EMAIL PROTECTED]> writes:
> Let me explain my posting which started this `thread':
> - The developer's FAQ section 1.9 explains why PostgreSQL doesn't use
> threads (and many times it has been discussed on the list).
> - The TODO list has an item `Experiment with multi-thr
Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Michael, please use bison 1.75 to update ecpg
>
> Why is this necessary? AFAIK we don't keep bison-derived files in
> CVS...
Right, they aren't in CVS, but they are shipped in the tarball so we
don't require everyone to have b
> -Original Message-
> From: Tom Lane [mailto:tgl@;sss.pgh.pa.us]
> Sent: 19 October 2002 17:17
> To: Bruce Momjian
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] /contrib/retep to gborg
>
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am concerned that removing them may c
10 matches
Mail list logo
