Re: temporary tables are logged somehow?

It means, that 8192 commits + 8192 "create temp table" (and drop it after
closing connection) costs me 48 MB of WAL files.
And there is no way to reduce disk space usage, right?
Does amount of data which has to be written to WAL-file depend on size of
transaction?

On 22 January 2015 at 18:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> > On Thu, Jan 22, 2015 at 11:06 PM, Andrey Lizenko <lizenko79(at)gmail(dot)com>
> wrote:
> >> 3. They are not WAL-logged.
> >> Whats wrong with it in my case?
>
> > Nothing. Temporary tables are not WAL-logged, but transaction commit is.
>
> Right. I think there is some optimization for transactions that only
> wrote temp-table data, but it could at most be skipping fsync of the
> transaction commit record, not omitting generating it entirely.
>
> Also, changes to the system catalogs are always WAL-logged; so creation
> and deletion of a temp table cause some amount of WAL output, even if
> manipulation of the table's contents does not.
>
> regards, tom lane
>

--
Regards, Andrey Lizenko