Re: : Re: [GENERAL] A strange problem

2005-08-28 Thread Tang Tim Hei
寄件者: Stephan Szabo [EMAIL PROTECTED] 日期: 2005/08/28 星期日 上午 09:03:20 HKT 收件者: Tang Tim Hei [EMAIL PROTECTED] 副本: pgsql-general@postgresql.org 主旨: Re: 回覆: Re: [GENERAL] A strange problem On Sun, 28 Aug 2005, Tang Tim Hei wrote: ±H¥???: Stephan Szabo [EMAIL PROTECTED] :

Re: [GENERAL] postgresql performance degradation over time....

2005-08-28 Thread Ben-Nes Yonatan
Bruno Wolff III wrote: On Sat, Aug 27, 2005 at 18:19:54 +0530, sunil arora [EMAIL PROTECTED] wrote: Bruno, thanks for the reply, we did run vaccum on it.. and we do it regulary to maintain its performance but its not giving the expected results. Did you do VACUUM FULL or just plain

Re: : Re: [GENERAL] A strange problem

2005-08-28 Thread Ragnar Hafstað
On Sun, 2005-08-28 at 16:22 +0800, Tang Tim Hei wrote: The following commands are little different from the previous one. (1) select A.* from test.currency A, test.price_list B where A.curr_cd=B.curr_cd and A.curr_cd='USD' (2) select A.* from test.currency A, test.price_list B, test.country

Re: : Re: [GENERAL] A strange problem

2005-08-28 Thread Stephan Szabo
On Sun, 28 Aug 2005, Tang Tim Hei wrote: Well, you have to write your queries to do what you want depending on such things. For example, the above doesn't constrain the join from currency and country and so you get multiple copies of the USD currency info for each country. If you want

Re: [GENERAL] About ERROR: must be *superuser* to COPY to or from a file

2005-08-28 Thread Tom Lane
Greg Stark [EMAIL PROTECTED] writes: In any case here's some quick results from my system. There seems to a greater than 21% slowdown associated with piping the data through two processes instead of reading directly. Well, if the penalty is order of 20% (as opposed to integer multiples) I

Re: [GENERAL] Problem upgrading from 8.0.1 to 8.0.3

2005-08-28 Thread Alvaro Herrera
On Thu, Aug 25, 2005 at 10:17:05AM -0300, Clodoaldo Pinto wrote: I was running 8.0.1 and PHP in FC3 with no problems. Then i upgraded to 8.0.3 using yum and yum installed postgresql-libs.i386 0:7.4.8-1.FC3.1. (Is it Ok?) It would have been better if it had picked postgresql-compat (or

[GENERAL] A real currency type

2005-08-28 Thread Martijn van Oosterhout
For a while I've been wondering about making a type that was really a shell around a base type that tagged the type in some way. For example, associating a currency with a numeric and complaining about additions between mismatches. Well, I did it and it's available here:

Re: [GENERAL] Problem upgrading from 8.0.1 to 8.0.3

2005-08-28 Thread Clodoaldo Pinto
2005/8/28, Alvaro Herrera [EMAIL PROTECTED]: On Thu, Aug 25, 2005 at 10:17:05AM -0300, Clodoaldo Pinto wrote: It would have been better if it had picked postgresql-compat (or whatever the name is for the package that has libpq3 in the 8.0.3 release). Probably if you install that package by

[GENERAL] boolean default value

2005-08-28 Thread Michael Schmidt
I've not been able to find anything on this in the groups or by Google. I have a table with several boolean columns, all not null and with either 'true' or 'false' as default values. I've been testing the system in pgAdmin III. When I insert a new record, all the boolean columns are set

Re: [GENERAL] boolean default value

2005-08-28 Thread Michael Fuhr
On Sun, Aug 28, 2005 at 03:31:17PM -0600, Michael Schmidt wrote: I've not been able to find anything on this in the groups or by Google. I have a table with several boolean columns, all not null and with either 'true' or 'false' as default values. I've been testing the system in pgAdmin III.

Re: [GENERAL] boolean default value

2005-08-28 Thread Michael Schmidt
Mr. Fuhr, Thanks for your quick response. In fact, the problem doesn't occur in psql or in EMS PostgreSQL Manager. It appears unique to pgAdmin III. In the future, I'll check such things with psql before asking a (potentially dumb) question. Again, thanks! Michael Schmidt

[GENERAL] stack depth limit exceeded

2005-08-28 Thread Jamie Deppeler
At the moment i am trying to execute a very simple function but i am getting the following error stack depth limit exceeded function CREATE OR REPLACE FUNCTION contacts.addContactField () RETURNS trigger AS $body$ begin update contacts.person set contact = new.firstname where

Re: [GENERAL] stack depth limit exceeded

2005-08-28 Thread Michael Fuhr
On Mon, Aug 29, 2005 at 12:01:59PM +1000, Jamie Deppeler wrote: At the moment i am trying to execute a very simple function but i am getting the following error stack depth limit exceeded That's often a sign of infinite recursion, i.e., a function that keeps calling itself, either directly or

Re: [GENERAL] stack depth limit exceeded

2005-08-28 Thread Tom Lane
Jamie Deppeler [EMAIL PROTECTED] writes: At the moment i am trying to execute a very simple function but i am getting the following error stack depth limit exceeded You didn't really show the complete context, but seeing that this is a trigger and it's trying to do an UPDATE person internally,

Re: [GENERAL] About ERROR: must be *superuser* to COPY to or from a file

2005-08-28 Thread John D. Burger
Well, they would have access to every world readable file on the system, ie /etc, /usr, /lib, ... most files are world readable. There's a lot of discussion about this, yet no-one has demonstrated that COPY FROM STDIN isn't just as good and avoids all the issues entirely. Well they're

Re: [GENERAL] stack depth limit exceeded

2005-08-28 Thread Jamie Deppeler
What i am trying to do is update the field contact with field values in firstname and lastname Trigger CREATE TRIGGER updateContact AFTER INSERT OR UPDATE ON FOR EACH ROW EXECUTE PROCEDURE contacts.addContactField(); Procedure CREATE OR REPLACE FUNCTION contacts.addContactField () RETURNS