Re: [GENERAL] Vacuum and state_change - Mailing list pgsql-general

From Adrian Klaver
Subject Re: [GENERAL] Vacuum and state_change
Date
Msg-id d6e0d57a-fb1a-0a62-4ce4-b5f838fb20ef@aklaver.com
Whole thread Raw
In response to Re: [GENERAL] Vacuum and state_change  (armand pirvu <armand.pirvu@gmail.com>)
Responses Re: [GENERAL] Vacuum and state_change  (armand pirvu <armand.pirvu@gmail.com>)
List pgsql-general
On 06/09/2017 02:01 PM, armand pirvu wrote:
>
>> On Jun 9, 2017, at 3:52 PM, Adrian Klaver <adrian.klaver@aklaver.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
moreprecise. We call them temporary since we do drop them after all is said and done. Maybe we should change the way we
callthem 

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.klaver@aklaver.com


pgsql-general by date:

Previous
From: Ken Tanzer
Date:
Subject: Re: [GENERAL] Limiting DB access by role after initial connection?
Next
From: Ken Tanzer
Date:
Subject: Re: [GENERAL] Limiting DB access by role after initial connection?