> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de D'Arcy J.M. Cain
> Envoyé : jeudi 27 juillet 2006 19:49
> À : Daniel Caune
> Cc : [EMAIL PROTECTED]; pgsql-admin@postgresql.org; pgsql-
> [EMAIL PROTECTED]
> Objet : Re: [SQL] PostgreSQL server terminat
Daniel CAUNE <[EMAIL PROTECTED]> writes:
> Actually it seems, from the source code, that a null slot->tts_tuple
> won't lead to a segmentation fault in function slot_attisnull, while
> slot and slot->tts_tupleDescriptor will.
I'll bet on D'Arcy's theory that slot is being passed in as NULL.
Exactl
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> De la part de Tom Lane
> Envoyé : jeudi 27 juillet 2006 19:26
> À : Daniel Caune
> Cc : pgsql-admin@postgresql.org; pgsql-sql@postgresql.org
> Objet : Re: [SQL] PostgreSQL server terminated by signal 11
>
> "Daniel
"Mark Liberman" <[EMAIL PROTECTED]> writes:
> <4983:2006-07-27 18:04:26 PDT>PANIC: could not open relation =
> 1663/128873/129201: No such file or directory
> <4981:2006-07-27 18:04:26 PDT>LOG: startup process (PID 4983) was =
> terminated by signal 6
That's really strange ... it's not supposed
Title: Corrupted DB - Help
Running postgres 8.1.2 on gentoo linux 2.6.14
Server crashed (not sure if due to pg operation). Upon rebooting server and trying to start postgres, get the following log entries:
<4983:2006-07-27 18:04:24 PDT>LOG: database system was interrupted at 2006-07-27 17
On Thu, 27 Jul 2006 19:00:27 -0400
"Daniel Caune" <[EMAIL PROTECTED]> wrote:
> I run the command responsible for creating the index and I entered "continue"
> in gdb for executing the command. After a while, the server crashes:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x080
"Daniel Caune" <[EMAIL PROTECTED]> writes:
> I run the command responsible for creating the index and I entered "continue"
> in gdb for executing the command. After a while, the server crashes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x08079e2a in slot_attisnull ()
> (gdb)
Please do not remove the list address from the Cc list when replying.
On Thu, 27 Jul 2006, roberto ms wrote:
System crashed after an unsuccessful drbd sync against a slave node. The
system was in production when I tried to drbd sync.
and has it been resolved?
Yes. I created another data po
> -Message d'origine-
> De : Tom Lane [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi, juillet 27, 2006 16:06
> À : Daniel Caune
> Cc : pgsql-sql@postgresql.org
> Objet : Re: [SQL] PostgreSQL server terminated by signal 11
>
> "Daniel Caune" <[EMAIL PROTECTED]> writes:
> > My PostgreSQL serve
Try running pgstattuple on some of the tables that have not had vacuum full, and some of those that have. It will tell you how many dead tuples there are in the table, which is an indicator of how seriously the table needs a full vacuum.
Run IPCS on the Unix command line to see how much of your
"Daniel Caune" <[EMAIL PROTECTED]> writes:
> I try to create an index on character varying(64) column but PostgreSQL
> complains that the index row size reaches the maximum limit:
> CREATE INDEX IDX_GSLOG_EVENT_ARCHIVE_GAME_CLIENT_VERSION
> ON GSLOG_EVENT_ARCHIVE(GAME_CLIENT_VERSION);
> ER
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] De la part de Jeff Frost
> Envoyé : jeudi, juillet 27, 2006 15:36
> À : Daniel Caune
> Cc : pgsql-admin@postgresql.org
> Objet : Re: [ADMIN] [SQL] PostgreSQL server terminated by signal 11
>
> On Thu, 27 Jul 2006, D
On Thu, 27 Jul 2006, Daniel Caune wrote:
Actually ulimit is unlimited for user postgres and when the server was
terminated the memory used was not that much compared to the machine capacity:
Mem: 2075860k total, 1663520k used, 412340k free, 5620k buffers
Swap: 369452k total,
Hi,
I try to create an index on character varying(64) column but PostgreSQL
complains that the index row size reaches the maximum limit:
CREATE INDEX IDX_GSLOG_EVENT_ARCHIVE_GAME_CLIENT_VERSION
ON GSLOG_EVENT_ARCHIVE(GAME_CLIENT_VERSION);
ERROR: index row requires 198468548 bytes, maximu
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] De la part de Jeff Frost
> Envoyé : jeudi, juillet 27, 2006 12:07
> À : Daniel Caune
> Cc : pgsql-sql@postgresql.org; pgsql-admin@postgresql.org
> Objet : Re: [SQL] PostgreSQL server terminated by signal 11
>
> On Thu, 27 Jul 2006, Daniel Caune
On Thu, 27 Jul 2006, Daniel Caune wrote:
My PostgreSQL server running on a Linux machine is terminated by signal
11 whenever I try to create some indexes on a table, which contains
quite a lot of data. However I succeeded in creating some other indexes
without having the PostgreSQL server termi
Nolan Cafferky wrote:
> The so far untried ideas I've had are:
>
> * Try out the autovacuum service
> * Re-index tables (this hasn't been done for at least months, maybe never)
> * Do some selective VACUUM FULL on high-use tables (materialized view
> for report seems like a likely culprit, but a
Synopsis: VACUUM ANALYZE on full database used to take just a few
minutes, now it takes several hours, with no apparant improvement in
successive runs.
Details:
I have a production database server hosting two heavily used databases
and not much else. We're currently running postgres 8.0.8.
That appears to be the JDBC driver is not able to connect to the PostgreSQL database.Try out the following:- See if there is any firewall running, run 'iptables -F" on the database server machine to disable it for a while and then test the same Java code
- Check the routing tables info and see if t
On Thu, 20 Jul 2006, Omer Mustafa wrote:
Connection refused. Check that the hostname and port are correct and that
the postmaster is accepting TCP/IP connections.
Exception: java.net.ConnectException: Connection refused: connect
On Sat, 22 Jul 2006, roberto ms wrote:
I get a message that says that permission is denied while creating
postmaster.pid.
I tried to list (ls -l) the .../data directory, and I get:
/usr/bin/ls: postmaster.pid: denied permission.
What does ls -ld .../data indicate? What caused the system cra
Please do not remove the list from the Cc when replying.
On Thu, 27 Jul 2006, Omer Mustafa wrote:
FATAL: no pg_hba.conf entry for host "203.26.95.33", user "sysloguser",
database "syslog"
but i have this entry in my pg_hba file.
Most likely it is because you didn't reload the postgresql ser
22 matches
Mail list logo
