From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Zero throughput on a query on a very large table. |
Date: | 2019-01-25 20:04:37 |
Message-ID: | 31319.1548446677@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> writes:
> Second, here is what i found and what messed us up.
> select current_setting('random_page_cost'); --> 4
> alter database "CMS_TMP" set random_page_cost=0.00000001;
> select current_setting('random_page_cost'); --> 4 ????
ALTER DATABASE only affects subsequently-started sessions.
> I also tried:
> select current_setting('random_page_cost'); --> 4
> select set_config('random_page_cost', '0.000001', true);
> select current_setting('random_page_cost'); --> 4 ????
That "true" means "local to the current transaction", which is
just the one statement if you don't have a BEGIN.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | ldh@laurent-hasson.com | 2019-01-25 20:31:21 | Re: Zero throughput on a query on a very large table. |
Previous Message | ldh@laurent-hasson.com | 2019-01-25 19:24:30 | Re: Zero throughput on a query on a very large table. |