// FIXED //
Tom, thank you so much for your help! Now running 8.1.2, the query now works
quickly and properly.
-Ben
On Wednesday 25 January 2006 13:17, Benjamin Smith wrote:
> Version: postgresql-8.1.0-4.c4
>
> I'll have to see about getting an update...
>
> Thanks a TON,
>
> -Ben
>
>
Hello Ben,
Unless I am wrong there is a set of RPMs available via the PostgreSQL site for
8.1.1/2 http://www.postgresql.org/ftp/binary/v8.1.2/linux/rpms/
Aly.
Benjamin Smith wrote:
Version: postgresql-8.1.0-4.c4
I'll have to see about getting an update...
Thanks a TON,
-Ben
Version: postgresql-8.1.0-4.c4
I'll have to see about getting an update...
Thanks a TON,
-Ben
On Wednesday 25 January 2006 13:11, you wrote:
> Benjamin Smith <[EMAIL PROTECTED]> writes:
> > Aha, yep. Sorry:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0043c82c in h
Benjamin Smith <[EMAIL PROTECTED]> writes:
> Aha, yep. Sorry:
> Program received signal SIGSEGV, Segmentation fault.
> 0x0043c82c in heap_modifytuple ()
> (gdb) bt
> #0 0x0043c82c in heap_modifytuple ()
> #1 0x0043c8f5 in slot_getattr ()
> #2 0x0047a50a in FormIn
Tom,
Since we host customer data, I have to get OK from the company attorney before
I can give you a full "howto create". I've been unable to recreate it without
a full database dump. I'm waiting for a call back on that. I also can't
recreate it on IA32.
I tried to replicate the issue on a u
Benjamin Smith <[EMAIL PROTECTED]> writes:
> OK, here's the output:
> (gdb) continue
> Continuing.
> Program received signal SIGSEGV, Segmentation fault.
> 0x0043c82c in heap_modifytuple ()
> (gdb)
> // not very hopeful, I'd think //
You forgot the
Stephen Frost <[EMAIL PROTECTED]> writes:
> * Tom Lane ([EMAIL PROTECTED]) wrote:
>> ps auxww | grep postgres:
>> ... eyeball determination of correct PID ...
> You can also do 'select pg_backend_pid();' from psql... I know that's
> there on 8.1, though I recall this was an 8.0 discussion and I *
OK, here's the output:
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x0043c82c in heap_modifytuple ()
(gdb)
// not very hopeful, I'd think //
Can I get a RHES/CENTOS PG 8.1 RPM with the symbols enabled? Unfortuna
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Benjamin Smith <[EMAIL PROTECTED]> writes:
> > What's the best way to do this? Take PG down (normally started as a
> > service)
> > and run directly in a single-user mode?
>
> No, just start a psql session in one window, then in another window
> determine
Benjamin Smith <[EMAIL PROTECTED]> writes:
> What's the best way to do this? Take PG down (normally started as a service)
> and run directly in a single-user mode?
No, just start a psql session in one window, then in another window
determine the PID of the backend process it's connected to, and
Thanks,
What's the best way to do this? Take PG down (normally started as a service)
and run directly in a single-user mode?
I've never reallly worked with gdb...
-Ben
On Tuesday 24 January 2006 17:27, you wrote:
> > What information do you need to help figure this out?
>
> Reproduce it
Benjamin Smith <[EMAIL PROTECTED]> writes:
> What information do you need to help figure this out?
Best is to provide a recipe by which someone else can reproduce it
from a standing start. You can find some useful hints at
http://www.postgresql.org/docs/8.1/static/bug-reporting.html
Benjamin Smith <[EMAIL PROTECTED]> writes:
> in /var/log/messages, I see
>
> Jan 24 17:00:04 kepler kernel: postmaster[26185]: segfault at
> 2516d728
> rip 0043c82c rsp 007fbfffddd0 error 4
>
> The insert statement is long, but doesn't seem to violate anything strange -
> n
I'm running PostgreSQL 8.1 on CentOS 4.2, Dual proc Athlon 64 w/4 GB RAM.
I'm trying to get a PHP app to work, but the failure happens when the command
is copy/pasted into pgsql. Trying to run a large insert statement, and I get:
server closed the connection unexpectedly
This probably
14 matches
Mail list logo
