Re: [PERFORM] Very slow query in PostgreSQL 9.3.3
2014-03-14 4:26 GMT+09:00 fburg...@radiantblue.com: PostgreSQL 9.3.3 RHEL 6.4 Total db Server memory 64GB (...) effective_cache_size = 48MB I'm not sure if this will help directly, but is the value for 'effective_cache_size' intentional? 48 *GB* would be a more likely setting. Regards Ian Barwick -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
Re: [PERFORM] Postgres upgrade, security release, where?
2013/4/4 Mark Kirkwood mark.kirkw...@catalyst.net.nz: On 02/04/13 21:47, Mark Kirkwood wrote: On 02/04/13 21:34, Dave Page wrote: On Mon, Apr 1, 2013 at 11:43 PM, Mark Kirkwood mark.kirkw...@catalyst.net.nz wrote: On 02/04/13 13:55, Bruce Momjian wrote: On Tue, Apr 2, 2013 at 09:40:07AM +0900, Ian Lawrence Barwick wrote: Due to the security nature of the release, the source and binaries will only be publicly available on April 4 --- there are no pre-release versions available. The PostgreSQL homepage has a big announcement saying PostgreSQL minor versions released!, including a mention of a security issue; unfortunately it's not obvious that this is for the prior 9.2.3 release and as the announcement of the upcoming security release ( http://www.postgresql.org/about/news/1454/ ) does not mention the new release number, methinks there is plenty of room for confusion :( It might be an idea to update the splash box with details of the upcoming release. I agree updating the spash box would make sense. Or perhaps include a date on said splashes, so we know when to panic :-) I've added the date to the splash. You can cease panicing now :-) ...wipes forehead... Nice - but at the risk of seeming ungrateful, it would be good to know what timezone said date referred to...in case people were waiting on an important announcement or something... :-) I'm guessing somewhere around the start of the business day US time on their east coast? Which means a late night for those of us on the early side of the International Date Line (I'm in Japan). I'll want to at least find out what the nature of the problem is before deciding whether I need to burn some late-nite oil... Regards Ian Barwick -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
Re: [PERFORM] Postgres upgrade, security release, where?
2013/4/2 Bruce Momjian br...@momjian.us: On Mon, Apr 1, 2013 at 05:10:22PM -0700, Tory M Blue wrote: So It was announced that there would be a security patch for all versions released on the 4th. I see it's been announced/released on the website, but the versions available show Feb dates. Should the source be current? Or does it take a while for source and other to be made available? Figured if the site says released, it should be available. Thanks Tory postgresql-9.2.3.tar.bz22013-02-07 15.6 postgresql-9.2.3.tar.bz210:25:10 MB postgresql-9.2.3.tar.bz2.md52013-02-07 59 postgresql-9.2.3.tar.bz2.md510:25:10 bytes postgresql-9.2.3.tar.gz postgresql-9.2.3.tar.gz 2013-02-07 20.5 10:25:12 MB postgresql-9.2.3.tar.gz.md5 2013-02-07 58 postgresql-9.2.3.tar.gz.md5 10:25:13 bytes Due to the security nature of the release, the source and binaries will only be publicly available on April 4 --- there are no pre-release versions available. The PostgreSQL homepage has a big announcement saying PostgreSQL minor versions released!, including a mention of a security issue; unfortunately it's not obvious that this is for the prior 9.2.3 release and as the announcement of the upcoming security release ( http://www.postgresql.org/about/news/1454/ ) does not mention the new release number, methinks there is plenty of room for confusion :( It might be an idea to update the splash box with details of the upcoming release. Regards Ian Barwick -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
Re: [PERFORM] PG_XLOG 27028 files running out of space
2013/2/14 Tory M Blue tmb...@gmail.com My postgres db ran out of space. I have 27028 files in the pg_xlog directory. I'm unclear what happened this has been running flawless for years. I do have archiving turned on and run an archive command every 10 minutes. I'm not sure how to go about cleaning this up, I got the DB back up, but I've only got 6gb free on this drive and it's going to blow up, if I can't relieve some of the stress from this directory over 220gb. What are my options? Thanks Postgres 9.1.6 slon 2.1.2 I can't give any advice right now, but I'd suggest posting more details of your setup, including as much of your postgresql.conf file as possible (especially the checkpoint_* and archive_* settings) and also the output of pg_controldata. Ian Barwick
