Re: BUG #14290: materialized view refresh doesn't use temp_tablespace

From: Rick Otten <rotten(at)windfish(dot)net>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14290: materialized view refresh doesn't use temp_tablespace
Date: 2016-08-24 21:35:44
Message-ID: f66e1fdf5e4a3d4fff6f174d7d254651@www.windfish.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)windfish(dot)net> writes:

Rick> Is t1 also the tablespace for your materialized view? (It isn't
Rick> 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 is
Rick> 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-08-25 02:21:27 Re: BUG #14293: update from bug? memory leak?
Previous Message Andrew Gierth 2016-08-24 20:14:37 Re: BUG #14290: materialized view refresh doesn't use temp_tablespace