Bill Thoen <[EMAIL PROTECTED]> writes:
> I'm a bit out of my depth with using these debugging tools and
> interpreting their results, but I think the problem is due to the output
> being just too big for interactive display.
Well, I can certainly believe it's related to the amount of data
involv
I'm a bit out of my depth with using these debugging tools and
interpreting their results, but I think the problem is due to the output
being just too big for interactive display. Using the same query with
tighter limits in the WHERE clause works perfectly. When I changed the
SQL script to writ
Bill Thoen <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x003054264571 in fputc () from /lib64/libc.so.6
> #1 0x0040dbc2 in print_aligned_text (title=0x0, headers=0x5665d0,
> cells=0x2f8fc010, footers=0x557c90,
> opt_align=0x557ef0 'l' , "rr", 'l' times>, "rl lll", opt
Bill Thoen <[EMAIL PROTECTED]> writes:
> As you requested, here's what bt in gbd reports:
> (gdb) bt
> #0 0x003054264571 in fputc () from /lib64/libc.so.6
> #1 0x0040dbd2 in print_aligned_text ()
> #2 0x0040f10b in printTable ()
> #3 0x0041020b in printQuery ()
> #4
As you requested, here's what bt in gbd reports:
(gdb) bt
#0 0x003054264571 in fputc () from /lib64/libc.so.6
#1 0x0040dbd2 in print_aligned_text ()
#2 0x0040f10b in printTable ()
#3 0x0041020b in printQuery ()
#4 0x00407906 in SendQuery ()
#5 0x00
Bill Thoen <[EMAIL PROTECTED]> writes:
> My PostgreSQL is working great for small SQL queries even from my large
> table (18 million records). But when I ask it to retrieve anything that
> takes it more than 10 minutes to assemble, it crashes with this
> "Segmentation Fault" error. I get so little
Martijn van Oosterhout escribió:
> That said, it would be nice if it returned an error instead of
> crashing.
In my opinion it isn't just a matter of "would be nice". It is a
possible bug that should be investigated.
A look at a stack trace from the crashing process would be the first
place to
On Wed, Aug 22, 2007 at 07:09:22AM -0600, Bill Thoen wrote:
> PostgreSQL Version is 8.1.5, running on Linux (Fedora Core 6). The last few
> lines in the Serverlog are:
> LOG: unexpected EOF on client connection
> LOG: transaction ID wrap limit is 1073746500, limited by database
> "postgres"
> LOG
On Wed, Aug 22, 2007 at 09:46:21AM +1200, Andrej Ricnik-Bay wrote:
> On 8/22/07, Bill Thoen <[EMAIL PROTECTED]> wrote:
> > How would you suggest I try to track down this problem?
> > Any suggestions?
> postgres version?
> Operating system?
> Anything in the log(s)?
PostgreSQL Version is 8.1.5, run
On Tue, Aug 21, 2007 at 04:38:42PM -0500, Scott Marlowe wrote:
> On 8/21/07, Bill Thoen <[EMAIL PROTECTED]> wrote:
> > How would you suggest I try to track down this problem?
> > I run the following query:
> >
> > SELECT a.* FROM compliance_2006 a, ers_regions b
> > WHERE a.fips_st_cd=b.fips_st
>
On 8/22/07, Bill Thoen <[EMAIL PROTECTED]> wrote:
> How would you suggest I try to track down this problem?
> Any suggestions?
postgres version?
Operating system?
Anything in the log(s)?
--
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
http://www.american.edu/ec
On 8/21/07, Bill Thoen <[EMAIL PROTECTED]> wrote:
> How would you suggest I try to track down this problem?
> I run the following query:
>
> SELECT a.* FROM compliance_2006 a, ers_regions b
> WHERE a.fips_st_cd=b.fips_st
> AND a.fips_cnty_cd=b.fips_cou AND b.region =1
> AND a.fips_st_cd='
12 matches
Mail list logo
