Fw: [PERFORM] Query performance issue with 8.0.0beta1

2004-09-01 Thread Stefano Bonnin
- Original Message - From: Stefano Bonnin [EMAIL PROTECTED] To: Josh Berkus [EMAIL PROTECTED] Sent: Monday, August 30, 2004 4:13 PM Subject: Re: [PERFORM] Query performance issue with 8.0.0beta1 This is my postgres.conf, I have changed only the work_mem and shared_buffers parameters.

Re: [PERFORM] Changing the column length

2004-09-01 Thread gnari
From: Michael Ryan S. Puncia [EMAIL PROTECTED] I am sorry that my question is out of line with this group(performance) but I need -general might be more appropriate an urgent help :-( .pls .. I need to know how to change the length of the column. add a new column, use update

Re: [PERFORM] Query performance issue with 8.0.0beta1

2004-09-01 Thread Stefano Bonnin
Server HP: Intel(R) Pentium(R) 4 CPU 2.26GHz RAM 1GB OS: RedHat 8 And the disk: kernel: megaide: driver version 05.04f (Date: Nov 11, 2002; 18:15 EST) kernel: megaide: bios version 02.06.07221605 kernel: megaide: LD 0 RAID1 status=ONLINE sectors=156297343 capacity=76317 MB drives=2

Re: [PERFORM] slower every day

2004-09-01 Thread Shridhar Daithankar
On Wednesday 01 Sep 2004 3:36 pm, G u i d o B a r o s i o wrote: Dear all, I am currently experiencing troubles with the performance of my critical's database. The problem is the time that the postgres takes to perform/return a query. For example, trying the \d tablename command takes

Re: [PERFORM] [ADMIN] slower every day

2004-09-01 Thread G u i d o B a r o s i o
The solution appeared as something I didn't know On the .conf file Previous situation: #log_something=false log_something=true Worst situation #log_something=false #log_something=true Nice situation log_something=false #log_something=true Ok, the problem was that I assumed that

Re: [PERFORM] [ADMIN] slower every day

2004-09-01 Thread Richard Huxton
G u i d o B a r o s i o wrote: Conclusion: If you comment a line on the conf file, and reload it, will remain in the last state. (either wast true or false, while I expected a default) Yes, that's correct. No, you're not the only one to have been caught out by this. -- Richard Huxton

Re: [PERFORM] [ADMIN] slower every day

2004-09-01 Thread Michael Paesold
This issue was resently discussed on hackers. It is a known issue, not very convinient for the user. Nevertheless it is not fixed in 8.0, but will perhaps be addressed in the next major release. (Remembering, it was a non-trivial thing to change.) Best Regards, Michael Paesold G u i d o B a r o

Re: [PERFORM] [ADMIN] slower every day

2004-09-01 Thread G u i d o B a r o s i o
Thanks for the reply, Been reading hackers of Aug 2004 and found the threads. It's a common habit to create two lines on the configuration files, in order to maintain the copy of the default conf file. I guess this should be the worst scenery for a freshly incoming DBA trying to put things

Re: [PERFORM] Changing the column length

2004-09-01 Thread Josh Berkus
Michael, I am sorry that my question is out of line with this group(performance) but I need an urgent help :-( .pls .. I need to know how to change the length of the column. In the future, try to provide more detail on your problem.Fortunately, I think I know what it is.

Re: [PERFORM] seqscan instead of index scan

2004-09-01 Thread Merlin Moncure
On Mon, 30 Aug 2004, Martin Sarsale wrote: Multicolumn indexes can only be used if the clauses involving the indexed columns are joined with AND. For instance, SELECT name FROM test2 WHERE major = constant OR minor = constant; You can use DeMorgan's Theorem to transform an OR clause to