From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | armand pirvu <armand(dot)pirvu(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Vacuum and state_change |
Date: | 2017-06-09 21:20:26 |
Message-ID: | d6e0d57a-fb1a-0a62-4ce4-b5f838fb20ef@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 06/09/2017 02:01 PM, armand pirvu wrote:
>
>> On Jun 9, 2017, at 3:52 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>>
>> On 06/09/2017 01:31 PM, armand pirvu wrote:
>>
>>>>
> By temporary tables I mean just regular table not tables created by "create temporary table" . I should have been more precise. We call them temporary since we do drop them after all is said and done. Maybe we should change the way we call them
You will want to look at this before making that decision:
https://www.postgresql.org/docs/9.6/static/sql-createtable.html
Temporary Tables
Basically, temporary tables are session specific.
>
> 9.5 but considering I can track what auto vacuum does I was thinking to use that as a reason to the upgrade advantage
It is nice, you just have to weigh against what effect the other changes:
https://www.postgresql.org/docs/9.6/static/release-9-6.html
might have on your setup.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Tanzer | 2017-06-09 21:20:29 | Re: Limiting DB access by role after initial connection? |
Previous Message | Ken Tanzer | 2017-06-09 21:16:46 | Re: Limiting DB access by role after initial connection? |