Re: BUG #14290: materialized view refresh doesn't use temp_tablespace - Mailing list pgsql-bugs

From Rick Otten
Subject Re: BUG #14290: materialized view refresh doesn't use temp_tablespace
Date
Msg-id f66e1fdf5e4a3d4fff6f174d7d254651@www.windfish.net
Whole thread Raw
In response to Re: BUG #14290: materialized view refresh doesn't use temp_tablespace  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-bugs

Aha.  Maybe that is my problem.  The refresh is silently failing to use TEMP_TABLESPACES.

When I explicitly do the grant create, the refresh then uses the temp tablespace as originally expected.

Thanks.

 

On 2016-08-24 16:14, Andrew Gierth wrote:

"Rick" == Rick Otten <rotten@windfish.net> writes:
 Rick> Is t1 also the tablespace for your materialized view? (It isn'tRick> clear from what you've posted below.)

No. The matview was created in pg_default.
Rick> In my environment my default tablespace for the database isRick> different than the temp_tablespace.

Possibly relevant here is that to put a tablespace into
temp_tablespaces, you must have CREATE permission on it. If you set the
value in postgresql.conf rather than with SET, you may not see errors
from lack of permission, instead tablespaces without permission will be
silently omitted.

 

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #14290: materialized view refresh doesn't use temp_tablespace
Next
From: Tom Lane
Date:
Subject: Re: BUG #14293: update from bug? memory leak?