Re: [GENERAL] php + postgresql website ?
http://www.skype.com/ On Tue, Jul 1, 2008 at 12:18 PM, Clemens Schwaighofer [EMAIL PROTECTED] wrote: --On Monday, June 30, 2008 08:06:25 PM +0800 paragasu [EMAIL PROTECTED] wrote: i can name a lot of website written in mysql and php. currently, i am planning to use postgresql database for my next project. i know there is a lot of testimonial about postgresql is better than mysql. can anyone please give me an example of website using postgresql database? I can't give you a direct example, but I use postgres for all of my webpages with database ranging from a view MB to up to several GB with tens of thausends of rows. I haven't had any trouble since the 5 years I am using it ... [ Clemens Schwaighofer -=:~ ] [ IT Engineer/Manager, TEQUILA\ Japan IT Group ] [6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jp ] -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] redundants indexes can be created
Hi guys, Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? postgres=# \d t1 Table public.t1 Column | Type | Modifiers +---+--- id | integer | not null name | character varying(20) | Indexes: t1_pkey PRIMARY KEY, btree (id) idx btree (id) idx2 btree (id) idx3 btree (id) idx4 btree (id) idx5 btree (id) Regards -- Cyril SCETBON -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
On Fri, Jul 04, 2008 at 11:54:37AM +0200, Cyril SCETBON wrote: Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? Why should it? Redundant indexes are not bugs. And can be very useful sometimes (thing concurrent reindexing). depesz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
Cyril SCETBON wrote: Hi guys, Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? Why should it stop you? Do you have an application that randomly generates indexes? -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
hubert depesz lubaczewski wrote: On Fri, Jul 04, 2008 at 11:54:37AM +0200, Cyril SCETBON wrote: Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? Why should it? Redundant indexes are not bugs. And can be very useful sometimes (thing concurrent reindexing). in this case your right, but lot of people are confused with primary key and unique key. So they create a unique key on the same column that constitute the primary key. For example, Oracle inhib it : SQL create table toto(id int primary key); Table created. SQL create unique index idx_toto_id on toto(id); create unique index idx_toto_id on toto(id) * ERROR at line 1: ORA-01408: such column list already indexed concurrent reindexing is the matter of postgresql, it should create it transparently when needed. And if I take into account the concurrent reindexing, why permitting more than 2 index on the same column ? -- Cyril SCETBON -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
Richard Huxton wrote: Cyril SCETBON wrote: Hi guys, Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? Why should it stop you? Do you have an application that randomly generates indexes? I'm just wondering why postgresql/mysql work like that. -- Cyril SCETBON -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
Cyril SCETBON wrote: Richard Huxton wrote: Cyril SCETBON wrote: Hi guys, Why postgres does not disallow creating redundants indexes ? Is it the same behaviour in postgresql 8.3 ? Why should it stop you? Do you have an application that randomly generates indexes? I'm just wondering why postgresql/mysql work like that. You ask for a particular index, it creates the index. Why complicate the code checking for possible duplicate indexes if it's not a problem people tend to encounter? -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
--On Freitag, Juli 04, 2008 11:26:31 +0100 Richard Huxton [EMAIL PROTECTED] wrote: You ask for a particular index, it creates the index. Why complicate the code checking for possible duplicate indexes if it's not a problem people tend to encounter? And what would characterize a duplicate index? Think about partial indexes, where we actually _want_ to have multiple indexes for certain ranges on the same column. -- Thanks Bernd -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] redundants indexes can be created
Bernd Helmle wrote: --On Freitag, Juli 04, 2008 11:26:31 +0100 Richard Huxton [EMAIL PROTECTED] wrote: You ask for a particular index, it creates the index. Why complicate the code checking for possible duplicate indexes if it's not a problem people tend to encounter? And what would characterize a duplicate index? Think about partial indexes, where we actually _want_ to have multiple indexes for certain ranges on the same column. this case is not included in duplicate index for me. -- Cyril SCETBON - Ingénieur bases de données AUSY pour France Télécom - OPF/PORTAILS/DOP/HEBEX Tél : +33 (0)4 97 12 87 60 Jabber : [EMAIL PROTECTED] France Telecom - Orange 790 Avenue du Docteur Maurice Donat Bâtiment Marco Polo C2 - Bureau 202 06250 Mougins France *** Ce message et toutes les pieces jointes (ci-apres le 'message') sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. *** This message and any attachments (the 'message') are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not recipient of this message, please cancel it immediately and inform the sender. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] simple installation problem in windows system
Many thanks Now I enter c:\Program Files\PostgreSQL\8.3\bin\createdb mydb; PG asks me password Is the password as superadmin's password or postgre's password what I set when postgresql installed in windows I try both, but does not work user administrator password fail so How to log on as superadmin. long On Thu, Jul 3, 2008 at 11:58 PM, Raymond O'Donnell [EMAIL PROTECTED] wrote: On 03/07/2008 14:40, Long Cui wrote: I install PostgreSQL 8.3.3 in Windows XP, and set Path environment viarable to C:\Program Files\PostgreSQL\8.3\bin, when I enter create database mydb; it successed, however when createdb mydb; told me syntax error. Dose the Path set wrong or I need to set other viarables? It sounds as if you're issuing the commands from within psql - hence the standard SQL create database works, but createdb.. won't. createdb is just a wrapper program that sends a create database... command to the server, so you need to run it from the Windows command-line. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland [EMAIL PROTECTED] Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals --
Re: [GENERAL] Delete from Join
Tom Lane wrote: Gwyneth Morrison [EMAIL PROTECTED] writes: What I am actually trying to get past is: DELETE FROM data_table1 using data_table2 INNER JOIN data_table1 ON data_table1.fkey = data_table2.pkey; The equivalent to that in Postgres would be DELETE FROM data_table1 USING data_table2 WHERE data_table1.fkey = data_table2.pkey; The fundamental issue here is that MSSQL expects the USING clause to contain a second reference to the delete target table, whereas PG does not --- if you write the table name again, that's effectively a self-join and you probably won't get the behavior you want. You can use JOIN syntax in USING in Postgres, but only for situations where the query really involves three or more tables. regards, tom lane Thank you Tom, That was exactly what I needed to know and yes it does work. I do know about the using/from clause and and the second table reference. Sorry about the above example, I cut it from something much larger to try and get my point across. Yes it is invalid. I should be more careful. I do have another question I will post as a separate posting. Gwyneth
Re: [GENERAL] xml and postgresql
aravind chandu wrote: Hi folks, I need to load xml data in to database can you tell me they way how do I import xml data into postgresql database. lets dat this is the xml file bookstore book category="CHILDREN" titleHarry Potter/title authorJ K. Rowling/author year2005/year price29.99/price /book book category="WEB" titleLearning XML/title authorErik T. Ray/author year2003/year price39.95/price /book /bookstore so finally the table name should be bookstore and column names are category,title, author,year,price and all the information in the xml file should be ported to the table can you please tell me how to do this its a bit confusing to me as i am just a beginner to this. Thanks in advance, Aravind. I have written a python program that may help you. It is part of a larger project I hope to post in a few days. Or I could sent it to you. Gwyneth
Re: [GENERAL] simple installation problem in windows system
On 04/07/2008 15:03, Long Cui wrote: Now I enter c:\Program Files\PostgreSQL\8.3\bin\createdb mydb; PG asks me password Is the password as superadmin's password or postgre's password what I set when postgresql installed in windows I try both, but does not work user administrator password fail so How to log on as superadmin. A lot of this basic stuff is pretty accessible in the documentation - have you read up on it there? Having said that, what you need to do is use the -U option to specify the Postgres user to use for the connection; if you don't, Postgres will try to authenticate you as the Windows account under which you're logged in. Look it up in the docs. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland [EMAIL PROTECTED] Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals -- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] 8.3 planner handling of IS NULL in aggregations
Hi, I've just noticed that the planner in 8.3.3 doesn't seem to realize the difference in the result of the following: SELECT col, COUNT(*) FROM tbl GROUP BY col; and SELECT col IS NULL, COUNT(*) FROM tbl GROUP BY col IS NULL; For a table with several million distinct values in col this makes quite a difference. I'd expect to be getting in memory hash aggregations, but I'm getting a sort step in there instead. Here's an example: SELECT col1 IS NOT NULL, col2 IS NOT NULL, col3 IS NOT NULL, COUNT(*) FROM tbl GROUP BY 1,2,3 ORDER BY 1,2,3; gives the following plan: GroupAggregate (cost=5018623.99..5387423.18 rows=4338999 width=12) - Sort (cost=5018623.99..5081536.33 rows=25164936 width=12) Sort Key: ((col1 IS NOT NULL)), ((col2 IS NOT NULL)), ((col3 IS NOT NULL)) - Seq Scan on tbl (cost=0.00..376989.36 rows=25164936 width=12) I can't see any way for it to produce more than 8 rows of output and so I'd expect a hash aggregate to be best. Removing the IS NOT NULLs from the expression gives basically the same plan and expected number of rows which then looks reasonable. Sam -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] simple installation problem in windows system
On 04/07/2008 15:36, Raymond O'Donnell wrote: Having said that, what you need to do is use the -U option to specify the Postgres user to use for the connection; if you don't, Postgres will try to authenticate you as the Windows account under which you're logged in. Look it up in the docs. or try createdb --help for a list of options. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland [EMAIL PROTECTED] Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals -- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] xml and postgresql
On Fri, Jul 4, 2008 at 11:01 AM, Gwyneth Morrison [EMAIL PROTECTED] wrote: aravind chandu wrote: Hi folks, I need to load xml data in to database can you tell me they way how do I import xml data into postgresql database. lets dat this is the xml file bookstore book category=CHILDREN Why category is not a Element of book, as all others? Is it a column of table bookstore? titleHarry Potter/title authorJ K. Rowling/author year2005/year price29.99/price /book book category=WEB titleLearning XML/title authorErik T. Ray/author year2003/year price39.95/price /book /bookstore so finally the table name should be bookstore and column names are category,title, author,year,price and all the information in the xml file should be ported to the table can you please tell me how to do this its a bit confusing to me as i am just a beginner to this. Thanks in advance, Aravind. I have written a python program that may help you. It is part of a larger project I hope to post in a few days. Or I could sent it to you. Gwyneth -- William Leite Araújo Pai 0.6 beta 2.1 Dizem que agora melhora...
[GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Hey all, Iam using PostgreSQL 8.2.3 on RHEL4 (Linux 2.6.20.3-custom #4 SMP x86_64 x86_64 x86_64 GNU/Linux). I have autovacuum tunrned off in the config, but it still seems to start up once everyday. What could be the cause of this ? TIA Dushyanth $ psql -U postgres postgres=# show autovacuum; autovacuum off (1 row) $ grep autovacuum postgresql.conf #autovacuum = off #autovacuum_naptime = 60 #autovacuum_vacuum_threshold = 1000 #autovacuum_analyze_threshold = 500 #autovacuum_vacuum_scale_factor = 0.4 #autovacuum_analyze_scale_factor = 0.2 #autovacuum_vacuum_cost_delay = -1 #autovacuum_vacuum_cost_limit = -1 # autovacuum processes postgres 16508 9.2 0.1 2310836 37984 ? Ds 09:58 0:09 \_ postgres: autovacuum process db1 postgres 19626 7.2 0.0 2289524 27704 ? Ds 10:09 0:03 \_ postgres: autovacuum process db1 postgres 20861 7.8 0.0 2298844 31028 ? Ds 10:13 0:08 \_ postgres: autovacuum process db1 postgres 21673 6.1 0.1 2336904 33400 ? Ds 10:16 0:12 \_ postgres: autovacuum process db1 postgres 21673 6.2 0.1 2339840 57400 ? Ds 10:16 0:31 \_ postgres: autovacuum process db1 postgres 13597 11.6 0.0 2358352 29936 ? Ds 17:12 0:20 \_ postgres: autovacuum process db2 postgres 13597 8.7 0.1 2358352 39056 ? Ds 17:12 0:41 \_ postgres: autovacuum process db2 postgres 13597 7.8 0.1 2363924 45540 ? Ds 17:12 1:01 \_ postgres: autovacuum process db2 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
On Friday 04 July 2008 7:51 am, Dushyanth wrote: Hey all, Iam using PostgreSQL 8.2.3 on RHEL4 (Linux 2.6.20.3-custom #4 SMP x86_64 x86_64 x86_64 GNU/Linux). I have autovacuum tunrned off in the config, but it still seems to start up once everyday. What could be the cause of this ? TIA Dushyanth From the docs: http://www.postgresql.org/docs/8.3/interactive/runtime-config-autovacuum.html autovacuum (boolean) Controls whether the server should run the autovacuum launcher daemon. This is on by default; however, track_counts must also be turned on for autovacuum to work. This parameter can only be set in the postgresql.conf file or on the server command line. --Note that even when this parameter is disabled, the system will launch autovacuum processes if necessary to prevent transaction ID wraparound. See Section 23.1.3 for more information. -- Adrian Klaver [EMAIL PROTECTED] -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] 8.3 planner handling of IS NULL in aggregations
Sam Mason [EMAIL PROTECTED] writes: I've just noticed that the planner in 8.3.3 doesn't seem to realize the difference in the result of the following: GROUP BY col; GROUP BY col IS NULL; Yeah, estimate_num_groups doesn't have any special knowledge about IS NULL -- it just sees this as an expression involving col. The general assumption about that is that the expression doesn't reduce the number of groups (think col + 1 for example). In general I'd rather it overestimated the number of groups than underestimated, so I don't think this heuristic is really wrong. Putting in a special case for IS NULL seems a bit silly, but maybe checking for a boolean result type would cover enough real-world uses to be worth the trouble? Not sure. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] 8.3 planner handling of IS NULL in aggregations
On Fri, Jul 04, 2008 at 12:37:48PM -0400, Tom Lane wrote: Yeah, estimate_num_groups doesn't have any special knowledge about IS NULL -- it just sees this as an expression involving col. The general assumption about that is that the expression doesn't reduce the number of groups (think col + 1 for example). In general I'd rather it overestimated the number of groups than underestimated, so I don't think this heuristic is really wrong. Hum, I thought it tried harder than that---I remembered date_trunc doing special things, but it doesn't seem to. Ah well! Putting in a special case for IS NULL seems a bit silly, but maybe checking for a boolean result type would cover enough real-world uses to be worth the trouble? Not sure. Sounds sensible. It would generalize nicely to the new enum types as well, use the minimum of the expected number of rows or the size of the result type's domain. Sam -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
-- Forwarded Message -- Subject: Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ? Date: Friday 04 July 2008 9:51 am From: dushy [EMAIL PROTECTED] To: Adrian Klaver [EMAIL PROTECTED] Hey, Thanks for the quick reply. From the docs: http://www.postgresql.org/docs/8.3/interactive/runtime-config-autovacuum.ht ml autovacuum (boolean) Controls whether the server should run the autovacuum launcher daemon. This is on by default; http://www.postgresql.org/docs/8.2/interactive/runtime-config-autovacuum.html Docs for 8.2 say its off by default. I did check the above link :), missed mentioning it here though. --Note that even when this parameter is disabled, the system will launch autovacuum processes if necessary to prevent transaction ID wraparound. See Section 23.1.3 for more information. Quoting that section : The maximum time that a table can go unvacuumed is two billion transactions minus the vacuum_freeze_min_age that was used when it was last vacuumed. If it were to go unvacuumed for longer than that, data loss could result. To ensure that this does not happen, the autovacuum facility described in Section 22.1.4 is invoked on any table that might contain XIDs older than the age specified by the configuration parameter autovacuum_freeze_max_age. (This will happen even if autovacuum is otherwise disabled.) db=# show vacuum_freeze_min_age; vacuum_freeze_min_age --- 1 (1 row) db=# show autovacuum_freeze_max_age; autovacuum_freeze_max_age --- 2 (1 row) None of the tables seem to have hit that limit. I executed the below query to check the age and they are all 200 million. Below are the unique age(relfrozenxid) for my tables. 161206586 161273308 193226476 76684520 Thanks Dushyanth Am forwarding back to list. One question? Did you do pg_ctl reload after changing the config file? -- Adrian Klaver [EMAIL PROTECTED] -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Dushyanth escribió: # autovacuum processes postgres 16508 9.2 0.1 2310836 37984 ? Ds 09:58 0:09 \_ postgres: autovacuum process db1 postgres 19626 7.2 0.0 2289524 27704 ? Ds 10:09 0:03 \_ postgres: autovacuum process db1 postgres 20861 7.8 0.0 2298844 31028 ? Ds 10:13 0:08 \_ postgres: autovacuum process db1 postgres 21673 6.1 0.1 2336904 33400 ? Ds 10:16 0:12 \_ postgres: autovacuum process db1 postgres 21673 6.2 0.1 2339840 57400 ? Ds 10:16 0:31 \_ postgres: autovacuum process db1 postgres 13597 11.6 0.0 2358352 29936 ? Ds 17:12 0:20 \_ postgres: autovacuum process db2 postgres 13597 8.7 0.1 2358352 39056 ? Ds 17:12 0:41 \_ postgres: autovacuum process db2 postgres 13597 7.8 0.1 2363924 45540 ? Ds 17:12 1:01 \_ postgres: autovacuum process db2 Something is seriously wrong here -- there should be only one autovacuum process ever in 8.2. Can you show a more complete ps tree, and perhaps include PPID in the listing? -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Hey, On Fri, Jul 4, 2008 at 10:56 PM, Adrian Klaver [EMAIL PROTECTED] wrote: Am forwarding back to list. One question? Did you do pg_ctl reload after changing the config file? I did not change any config yet - autovacuum was always disabled since the day PG was set up. Thanks Dushyanth -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Hey, # autovacuum processes postgres 16508 9.2 0.1 2310836 37984 ? Ds 09:58 0:09 \_ postgres: autovacuum process db1 postgres 19626 7.2 0.0 2289524 27704 ? Ds 10:09 0:03 \_ postgres: autovacuum process db1 postgres 20861 7.8 0.0 2298844 31028 ? Ds 10:13 0:08 \_ postgres: autovacuum process db1 postgres 21673 6.1 0.1 2336904 33400 ? Ds 10:16 0:12 \_ postgres: autovacuum process db1 postgres 21673 6.2 0.1 2339840 57400 ? Ds 10:16 0:31 \_ postgres: autovacuum process db1 postgres 13597 11.6 0.0 2358352 29936 ? Ds 17:12 0:20 \_ postgres: autovacuum process db2 postgres 13597 8.7 0.1 2358352 39056 ? Ds 17:12 0:41 \_ postgres: autovacuum process db2 postgres 13597 7.8 0.1 2363924 45540 ? Ds 17:12 1:01 \_ postgres: autovacuum process db2 Something is seriously wrong here -- there should be only one autovacuum process ever in 8.2. Can you show a more complete ps tree, and perhaps include PPID in the listing? My bad - I messed up the above. I grepped for autovacuum in my process logs and included all matches. There is only one autovacuum process when it starts up. Below is the correct output from one of the logs postgres 8951 0.0 0.1 2270284 60484 pts/0 SJun29 0:36 /usr/local/postgres/pgsql-8.2.3/bin/postgres -D /usr/local/postgres/current/data -i postgres 8989 4.9 0.0 57496 948 ?Ss Jun29 282:33 \_ postgres: logger process postgres 9002 0.0 6.4 2271532 2126852 ? Ss Jun29 2:13 \_ postgres: writer process postgres 9003 0.0 0.0 58564 1024 ?Ss Jun29 0:01 \_ postgres: archiver process postgres 9004 0.0 0.0 58448 832 ?Ss Jun29 0:00 \_ postgres: stats collector process postgres 871 0.0 0.1 2274216 36200 ? Ss Jul02 0:00 \_ postgres: postgres dbname [local] idle postgres 16508 9.2 0.1 2310836 37984 ? Ds 09:58 0:09 \_ postgres: autovacuum process dbname Thanks Dushyanth -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
dushy escribió: My bad - I messed up the above. I grepped for autovacuum in my process logs and included all matches. Ah, ok -- that makes more sense. There is only one autovacuum process when it starts up. Below is the correct output from one of the logs Good. Do you have entries in the pg_autovacuum table in this database? -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] [Postgresql 8.2.3] autovacuum starting up even after disabling ?
Hey, There is only one autovacuum process when it starts up. Below is the correct output from one of the logs Good. Do you have entries in the pg_autovacuum table in this database? No. Its empty. TIA Dushyanth -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
