Re: [SQL] Profiling tool for postgres under win32

2009-11-30 Thread aymen marouani
Hi, I'm sorry and thanks for the help, concerning your question : "Out of interest, how are you talking to PostgreSQL? Hand-written SQL via JDBC? Hibernate / TopLink / some other ORM (possibly via JPA)?" I'm using JPA/Toplink to talk to the PostgresSQL, and I asked my question about profiling bec

Re: [SQL] Profiling tool for postgres under win32

2009-11-30 Thread Craig Ringer
On 30/11/2009 4:42 PM, aymen marouani wrote: Hi, I'm sorry and thanks for the help, concerning your question : "Out of interest, how are you talking to PostgreSQL? Hand-written SQL via JDBC? Hibernate / TopLink / some other ORM (possibly via JPA)?" I'm using JPA/Toplink to talk to the PostgresS

[SQL] Schema's, roles and privileges

2009-11-30 Thread Michael Gould
I have a database with a schema called ISS. This is where all of our application definitions are stored. We did add 2 contribute modules (citext) and guid generator and both of these by default went to the public schema. It is our intent to not allow any access to public by our users. A few questi

Re: [SQL] Schema's, roles and privileges

2009-11-30 Thread Adrian Klaver
On Monday 30 November 2009 6:50:27 am Michael Gould wrote: > I have a database with a schema called ISS. This is where all of our > application definitions are stored. We did add 2 contribute modules > (citext) and guid generator and both of these by default went to the public > schema. It is our i

Re: [SQL] Schema's, roles and privileges

2009-11-30 Thread Michael Gould
Thanks Mike Gould "Adrian Klaver" wrote: > On Monday 30 November 2009 6:50:27 am Michael Gould wrote: >> I have a database with a schema called ISS. This is where all of our >> application definitions are stored. We did add 2 contribute modules >> (citext) and guid generator and both of these by

Re: [SQL] Schema's, roles and privileges

2009-11-30 Thread Harald Fuchs
In article <200911300708.12397.akla...@comcast.net>, Adrian Klaver writes: > From a quick look it would seem the easiest solution would be to change the > search_path in: > citext.sql.in > uuid-ossp.sql.in > These files are found in the respective contrib directories. Uninstall the > modules.

Re: [SQL] How to start the "auto_explain" module

2009-11-30 Thread Jaime Casanova
On Thu, Nov 26, 2009 at 6:26 AM, aymen marouani wrote: > > How can I load the auto_explain module ? > http://www.postgresql.org/docs/8.4/static/auto-explain.html -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387

[SQL] pg_restore followed by immediate VACUUM ANALYZE

2009-11-30 Thread Bryce Nesbitt
I looking at a script that does a pg_restore followed by an immediate VACUUM ANALYZE (postgres 8.3). I'm told that without the VACUUM ANALYZE the database will run slow. Does this ring true? Does pg_restore not update the query planner statistics? -- Sent via pgsql-sql mailing list (pgsql-sq

Re: [SQL] pg_restore followed by immediate VACUUM ANALYZE

2009-11-30 Thread Tom Lane
Bryce Nesbitt writes: > I looking at a script that does a pg_restore followed by an immediate > VACUUM ANALYZE (postgres 8.3). That's standard. > Does pg_restore not update the query planner statistics? Correct. Autovacuum might fix them eventually, but usually it's worth forcing the issue on

Re: [SQL] pg_restore followed by immediate VACUUM ANALYZE

2009-11-30 Thread Bryce Nesbitt
Tom Lane wrote: Does pg_restore not update the query planner statistics? Correct. Autovacuum might fix them eventually, but usually it's worth forcing the issue once you've completed your data loading. (This might involve multiple steps, which is why pg_restore doesn't try t

Re: [SQL] pg_restore followed by immediate VACUUM ANALYZE

2009-11-30 Thread Tom Lane
Bryce Nesbitt writes: >> Correct. Autovacuum might fix them eventually, but usually it's >> worth forcing the issue once you've completed your data loading. >> (This might involve multiple steps, which is why pg_restore >> doesn't try to force it for you.) > Hmm.  It seems like pg_restore would