SV: SV: Refreshing materialized views

Поиск
Список
Период
Сортировка
От Henrik Uggla
Тема SV: SV: Refreshing materialized views
Дата
Msg-id 2886758ebe314e13a73fb27f5c7d6cd4@kristianstad.se
обсуждение исходный текст
Ответ на Re: SV: Refreshing materialized views  (Ben Primrose <bprimrose@tracelink.com>)
Список pgsql-general
I finally managed to sort out all needed permissions and mappings.
Thanks for all replies!

cheers
Henrik
________________________________________
Från: Ben Primrose <bprimrose@tracelink.com>
Skickat: den 29 november 2017 12:42:56
Till: Daevor The Devoted
Kopia: hendrik.uggla@kristianstad.se; pgsql-general@lists.postgresql.org
Ämne: Re: SV: Refreshing materialized views

It may be simpler to just run the query from the materialized view definition as the user that you want to refresh the
mv.

On Tue, Nov 28, 2017 at 10:30 PM, Daevor The Devoted <dollien@gmail.com<mailto:dollien@gmail.com>> wrote:


On 28 Nov 2017 5:18 pm, "Tom Lane" <tgl@sss.pgh.pa.us<mailto:tgl@sss.pgh.pa.us>> wrote:
Henrik Uggla <Henrik.Uggla@kristianstad.se<mailto:Henrik.Uggla@kristianstad.se>> writes:
> The underlying tables are foreign tables. The user has been mapped to a foreign user with select permission. I have
noproblem 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
justfrom one of the foreign tables, then attempt the REFRESH. If that works, then keep adding more tables from your
originalmaterialized 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



--

Ben Primrose  |  Postgres DBA |  TraceLink Inc.
400 Riverpark Dr.
Floor 2, Suite 200
North Reading, MA 01864
o: +1.978.396.6507
e: bprimrose@tracelink.com<mailto:bprimrose@tracelink.com>



В списке pgsql-general по дате отправления:

Предыдущее
От: Swapnil Vaze
Дата:
Сообщение: Re: vacuumdb fails with error pg_statistic_relid_att_inh_indexconstraint violation after upgrade to 9.6
Следующее
От: Ted Toth
Дата:
Сообщение: Re: large numbers of inserts out of memory strategy