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 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
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
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.
I am assuming this problem and the other rash of Win32 problems reported
in March are now all fixed in 8.1.4. If not, please let me know.
---
Tom Lane wrote:
> I wrote:
> > "Peter Brant" <[EMAIL PROTECTED]> writes:
> >> Doe
Really? If there was a patch, I missed it.
My recollection is that there was general agreement about this
particular problem (see, for example,
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00189.php ), but
things kind of trailed off after that without a resolution.
As far as the complete
Peter Brant wrote:
> Really? If there was a patch, I missed it.
>
> My recollection is that there was general agreement about this
> particular problem (see, for example,
> http://archives.postgresql.org/pgsql-bugs/2006-04/msg00189.php ), but
> things kind of trailed off after that without a reso
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
The following bug has been logged online:
Bug reference: 2483
Logged by: Klaus Guntermann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux
Description:Wrong error report about missing entry in from clause
Details:
Hi,
with the follo
Hi, Devrim,
Thank you for your quick response.
I'll be pleased to get the newly spun RPM.
Thanks in advance,
Tetsuo SAKATA.
Devrim GUNDUZ wrote:
> Hi,
>
> On Thu, 2006-06-15 at 07:11 +, Tetsuo Sakata wrote:
>
>>I found an error when I tried to install an RPM
>>postgresql-docs-8.1.4-1PGDG.
"Klaus Guntermann" <[EMAIL PROTECTED]> writes:
> with the following simplified example I get a false error message in the
> second select statement, which is almost like the first one.
> select dummy.myfield from dummy where dummy.myfield=1 union
> select dummy.myfield from dummy where dummy.myfie
12 matches
Mail list logo
