Alle 07:36, venerdì 16 giugno 2006, hai probabilmente scritto:
> On Thu, Jun 15, 2006 at 11:48:37PM -0400, Tom Lane wrote:
> > "Emilia Venturato" <[EMAIL PROTECTED]> writes:
> > > Postgis developper said it could be a postgresql bug.
> >
> > Or it could be a postgis bug. Without a test case we can
Alle 16:18, venerdì 16 giugno 2006, Tom Lane ha probabilmente scritto:
>
> Emilia might have found some corner case where it doesn't, though;
> perhaps a malloc call that's not error-checked. A stack trace from
> the psql core dump would be useful.
>
> regards, tom lane
Cor
Emilia Venturato <[EMAIL PROTECTED]> writes:
> Alle 16:18, venerdì 16 giugno 2006, Tom Lane ha probabilmente scritto:
>> Emilia might have found some corner case where it doesn't, though;
>> perhaps a malloc call that's not error-checked. A stack trace from
>> the psql core dump would be useful.
Michael Fuhr <[EMAIL PROTECTED]> writes:
> That's a lot of data -- are you aware that psql (via libpq) fetches
> the entire result set before displaying it? In most cases 18444
> rows wouldn't be a problem, but with rows that wide it becomes a
> big problem because the client has to store it all i
On Fri, Jun 16, 2006 at 06:53:28AM -0600, Michael Fuhr wrote:
> The query plan shouldn't affect psql's behavior but selecting
> different columns might. Notice that the estimated column width
> is much higher when you select the geometry column than when you
> don't:
>
> [with]
> > Merge Join (c
On Fri, Jun 16, 2006 at 11:16:50AM +0200, Emilia Venturato wrote:
> > Did the segmentation fault leave a core dump in your $PGDATA directory
> > or somewhere beneath it? If not then you might need to adjust your
> > coredumpsize resource limit.
>
> I understand it was psql to crash, not postgresq
On Thu, Jun 15, 2006 at 11:48:37PM -0400, Tom Lane wrote:
> "Emilia Venturato" <[EMAIL PROTECTED]> writes:
> > Postgis developper said it could be a postgresql bug.
>
> Or it could be a postgis bug. Without a test case we can use to
> reproduce the problem, it's all speculation. Please send a co
"Emilia Venturato" <[EMAIL PROTECTED]> writes:
> Postgis developper said it could be a postgresql bug.
Or it could be a postgis bug. Without a test case we can use to
reproduce the problem, it's all speculation. Please send a complete,
self-contained test case...
regards
The following bug has been logged online:
Bug reference: 2481
Logged by: Emilia Venturato
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Debian etch
Description:select from table's join with geometries doesn't go
Details:
--I have data
