On Wed, Dec 22, 2010 at 3:24 PM, Fujii Masao wrote:
> On Wed, Dec 22, 2010 at 11:48 AM, Tom Lane wrote:
>> Fujii Masao writes:
>>> The proposed patch looks very simple. I don't think that applying that
>>> patch will cause serious risk.
>>
>> Maybe so, maybe not, but *it won't get tested* to any
On Wed, Dec 22, 2010 at 11:48 AM, Tom Lane wrote:
> Fujii Masao writes:
>> The proposed patch looks very simple. I don't think that applying that
>> patch will cause serious risk.
>
> Maybe so, maybe not, but *it won't get tested* to any meaningful degree
> if it's applied.
Umm.. I don't have go
On Mon, Dec 20, 2010 at 9:48 PM, Maxim Boguk wrote:
> Anyone can enlighten me what happens here?
That does look weird, but without a simple test case I think it's
going to be hard to investigate this. Installing Slony and your code
and building a 130GB is more effort than I'm willing to put in..
Robert Haas writes:
> Are you saying that this problem does not exist in 8.3.0 but does
> exist in later 8.3.x revs?
I believe it dates from
Author: Tom Lane
Branch: master Release: REL8_4_BR [c98a92378] 2008-12-13 02:00:20 +
Branch: REL8_3_STABLE Release: REL8_3_6 [8d1d6019d] 2008-12-13 02
On Tue, Dec 21, 2010 at 9:26 PM, Fujii Masao wrote:
> On Fri, Dec 17, 2010 at 7:27 AM, Tom Lane wrote:
>> Tatsuhito Kasahara writes:
>>> When I tested simple query as following, backend process used much memory
>>> and not freed until the backend was finished.
>>> # This is reproduced on Postgre
Fujii Masao writes:
> The proposed patch looks very simple. I don't think that applying that
> patch will cause serious risk.
Maybe so, maybe not, but *it won't get tested* to any meaningful degree
if it's applied.
> Unless the bug is fixed, the users who encountered the memory-leak
> cannot upd
On Fri, Dec 17, 2010 at 7:27 AM, Tom Lane wrote:
> Tatsuhito Kasahara writes:
>> When I tested simple query as following, backend process used much memory
>> and not freed until the backend was finished.
>> # This is reproduced on PostgreSQL8.3 (PostgreSQL8.3.6 - PostgreSQL8.3.12)
>
> Hmm ... thi
The following bug has been logged online:
Bug reference: 5800
Logged by: Carlo Curatolo
Email address: genam...@brutele.be
PostgreSQL version: 9.0.2 64bits
Operating system: Windows 7 64bits
Description:"corrupted" error messages (encoding problem ?)
Details:
On a n
"Sandro Santilli" writes:
> SELECT a, b, ST_RelateMatch(a,b) FROM
> ( SELECT '101202FFF' as a, 'TTFFF' as b) as f;
> Results in:
> ERROR: failed to find conversion function from unknown to text
Cast those unknown literals to text explicitly, ie
SELECT a, b, ST_RelateMatch(a,b) FROM
Apologies for the delay in replying.
On Sat, Nov 13, 2010 at 1:27 AM, Kasia Tuszynska wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5752
> Logged by: Kasia Tuszynska
> Email address: ktuszyn...@esri.com
> PostgreSQL version: 9.0.1
> Operating system:
The following bug has been logged online:
Bug reference: 5799
Logged by: Sandro Santilli
Email address: s...@keybit.net
PostgreSQL version: 8.4.3
Operating system: GNU/Linux 64bit
Description:failed to find conversion function from unknown to text
Details:
Function
11 matches
Mail list logo
