Hello,
Out of curiosity, since there's CREATE TEMP VIEW, any particular reason
there's no CREATE TEMP MATERIALIZED VIEW?
Seems like it could be similar to a temp table.
Hi,
On Fri, 31 May 2019 at 17:43, Andrew Gierth
wrote:
> >>>>> "Ivan" == Ivan Voras writes:
>
> Ivan> Since AFAIK temp tables are very close to unlogged ordinary
> Ivan> tables, what would stop this feature from being implemented?
>
> The key d
hi,
On Fri, 31 May 2019 at 17:54, Christopher Browne wrote:
> 2. Temp tables are only associated (and visible) in the session in which
> you are doing the work. autovacuum operates inside an ordinary session
> context, and in a separate connected session, so it can't see your temp
> tables; t
On Fri, 31 May 2019 at 17:38, Adam Brusselback
wrote:
> Temp tables are not visibile outside of a single connection, so the
> autovacuum worker connection isn't able to see it.
>
I can connect as a superuser via psql while temp tables are being used and
I can examine tables in the pg_temp_* sche
On Fri, 31 May 2019 at 17:34, Pavel Stehule wrote:
> Hi
>
> pá 31. 5. 2019 v 17:26 odesílatel Ivan Voras napsal:
>
>> Hello,
>>
>>
>> autovacuum check tables once per minute, and working on closed
> transactions. Lot of times temporary tables are filled in
Hello,
The reason why we are using temp tables is to allow concurrent runs on some
very large reports which involve creating and heavily churning dozens of
very large tables.
The problem we're facing is that if we DON'T use temp tables, the reports
finish in a couple of hours. If we DO use temp t
Hello,
I got a sort of POLA violation moment today - a colleague has restored a
PITR archive up to a point in time, and when the developers looked at the
data, it looked wrong - as it if wasn't from that particular time. Later,
he told me he got an error trying to use pg_dump to extract the desire
