[ADMIN] Diagnosing Postgres Segfault

Early this morning one of our databases suffered a segfault. The only note on this in /var/log/messages was: Nov 29 03:34:07 servername kernel: postmaster[18265]: segfault at 17b82000 rip 003c45e7c266 rsp 7fff2ca1b7d8 error 4 (replaced actual server name with servername) The

Re: [ADMIN] Diagnosing Postgres Segfault

Doesn't look like it at the moment. I'll see if we can get that setup and go from there. Thanks. -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Monday, November 29, 2010 4:10 PM To: Michael Holt Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Diagnosin

Re: [ADMIN] using limit

Yes, a limit should speed up your query from the sounds of things. *From:* Anibal David Acosta [mailto:a...@devshock.com] *Sent:* Thursday, December 16, 2010 11:34 AM *To:* 'Michael Holt'; pgsql-admin@postgresql.org *Subject:* RE: [ADMIN] using limit Is a table with 10 million of r

Re: [ADMIN] using limit

This really depends on the type of query you’re talking about. If there’s only one row in the table you’re querying then no, I don’t think it’ll change anything. If you’re querying a single row using a primary key it shouldn’t change anything. If you’re doing an aggregate query, say a sum of a bunc

[ADMIN] Seems like a large amount of xlog files

bles. So i have two questions: 1) Does simply running a transaction (implicit or explicit) cause writing to the WAL? 2) Is there any simple way to track what may be causing WAL writes? Alternatively, is there a simple way to see what is being recorded in these files? -- *Michael Holt*, *Databas

[ADMIN] Streaming replication status and fail over questions

to fail over, is there anyway for slaves to detect the new master? Without this it seems like fail over could be pretty messy. 3) Finally just wanted to confirm that SR allows only for replication of an entire server. -- *Michael Holt*, *Database Administrator* | TERAPEAK 2307-4464 Markham St

[ADMIN] max_locks_per_transaction and partitioned tables

to increase the max_locks_per_transaction. If the parent table is queried will it require a lock for each one of the child tables? I'm guessing it will. -- Michael Holt | Manager, Data Services | Linkedin Profile<http://ca.linkedin.com/pub/michael-holt/48/a21/5ab> mich...@terapeak.com&l

Re: [ADMIN] max_locks_per_transaction and partitioned tables

Thanks Tom. In the original plan a query of this sort was never supposed to happen, but it looks like some coding issues may have allowed it. -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: September-19-12 2:04 PM To: Michael Holt Cc: pgsql-admin@postgresql.org

[ADMIN] max_locks_per_transaction and partitioned tables

to increase the max_locks_per_transaction. If the parent table is queried will it require a lock for each one of the child tables? I'm guessing it will. -- Michael Holt | Manager, Data Services | Linkedin Profile<http://ca.linkedin.com/pub/michael-holt/48/a21/5ab> mich...@terapeak.com&l

Re: [ADMIN] Getting

Of course you can also see what the query plan will be without having to run the query through a standard explain query: http://www.postgresql.org/docs/9.0/static/sql-explain.html From: pgsql-admin-ow...@postgresql.org [pgsql-admin-ow...@postgresql.org] on behalf