Mike Landis wrote:
I am trying to experiment with the libpqxx API and postgresql 8.4.1 on a
32-bit
Vista machine. Libpqxx wants release and debug libraries for libpq
available.
Why libpqxx want the debug library?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
The following bug has been logged online:
Bug reference: 5238
Logged by: Daniel Nagy
Email address: nagy.dan...@telekom.hu
PostgreSQL version: 8.4.1
Operating system: Debian Lenny 5.0.3 x86_64. Kernel: 2.6.31.6-grsec
Description:frequent signal 11 segfaults
Details:
Daniel Nagy nagy.dan...@telekom.hu writes:
The binaries are not stripped, how can I help finding the cause?
Get a stack trace from the core dump using gdb.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I'm not an expert on this area of the code, but can we just ignore
isNatural and usingClause when deparsing?
No. These properties are *not* ignorable because doing so changes the
Robert == Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
My reading of the spec is that USING (and therefore NATURAL) is
defined to join identically named columns. Therefore, renaming
one of the input columns as the OP
On Thu, Dec 10, 2009 at 10:48 AM, Andrew Gierth
and...@tao11.riddles.org.uk wrote:
Robert == Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
My reading of the spec is that USING (and therefore NATURAL) is
defined to join
Andrew Gierth and...@tao11.riddles.org.uk writes:
There's another possible solution (albeit a somewhat nontrivial one)
which came up when a bunch of us were talking about this one on IRC;
which is to handle the problem in the view deparse: if a column used
in a USING clause has been renamed,
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Gierth and...@tao11.riddles.org.uk writes:
There's another possible solution (albeit a somewhat nontrivial one)
which came up when a bunch of us were talking about this one on IRC;
which is to handle the problem in the
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 1:46 AM, Tom Lane t...@sss.pgh.pa.us wrote:
My reading of the spec is that USING (and therefore NATURAL) is defined
to join identically named columns.
Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem with USING is that it is not merely a join condition but
affects the set of columns emitted by the join. It can't be converted
to a simple ON without changing the
On Thu, Dec 10, 2009 at 1:02 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Robert Haas escribió:
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Hmm. Cute, but I wonder why we shouldn't just be throwing an error.
As I said last night, the only thing I see wrong
On Thu, Dec 10, 2009 at 12:32 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Dec 10, 2009 at 11:54 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem with USING is that it is not merely a join condition but
affects the set of columns emitted by the
The following bug has been logged online:
Bug reference: 5239
Logged by: Recursive complex query
Email address: gusta1...@gmail.com
PostgreSQL version: 8.4
Operating system: Windows XP SP 2
Description:Recursive complex query
Details:
I try to run following query:
Recursive complex query gusta1...@gmail.com writes:
and the server report me the error: ERROR: write failed
Maybe you ran out of disk space? Are you sure the recursion terminates
at all, or does so before generating an enormous number of rows?
regards, tom lane
--
On 10/12/2009 5:12 AM, Daniel Nagy wrote:
The following bug has been logged online:
Bug reference: 5238
Logged by: Daniel Nagy
Email address: nagy.dan...@telekom.hu
PostgreSQL version: 8.4.1
Operating system: Debian Lenny 5.0.3 x86_64. Kernel: 2.6.31.6-grsec
Description:
15 matches
Mail list logo
