Re: SV: Refreshing materialized views - Mailing list pgsql-general

From Daevor The Devoted
Subject Re: SV: Refreshing materialized views
Date
Msg-id CAAZnbVoxfchioGbiT5edqz+qJzJETOyLM=9EUy64aVzyCwAMqw@mail.gmail.com
Whole thread Raw
In response to Re: SV: Refreshing materialized views  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SV: Refreshing materialized views
List pgsql-general
On 28 Nov 2017 5:18 pm, "Tom Lane" wrote: Henrik Uggla writes: > The underlying tables are foreign tables. The user has been mapped to a foreign user with select permission. I have no problem selecting from the foreign tables or the materialized views. [ shrug... ] WFM; if I can select from the foreign table then I can make a materialized view that selects from it, and that refreshes without complaint. Admittedly, getting things set up to select from the foreign table is trickier than it sounds: your local user needs SELECT on the foreign table plus a mapping to some remote userid, and *on the remote server* that remote userid needs SELECT on whatever the foreign table is referencing. I'm guessing you messed up one of these components. regards, tom lane Hendrik, perhaps an easy way to check out Tom's suggestion is to create a very simple materialized view that selects just from one of the foreign tables, then attempt the REFRESH. If that works, then keep adding more tables from your original materialized view until you have found the problem. Basically, reduce the problem to the simplest case, and if that works, then keep adding to it until you hit the problem. You may still not know why the problem is happening, but you'll at least know where to focus any further investigation. Kind regards, Daevor, The Devoted

pgsql-general by date:

Previous
From: Brian Crowell
Date:
Subject: Re: large numbers of inserts out of memory strategy
Next
From: Tom Lane
Date:
Subject: Re: large numbers of inserts out of memory strategy