Re: [HACKERS] Inherited constraints and search paths (was Re:

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: [HACKERS] Inherited constraints and search paths (was Re:
Дата
в 18:31:03
Msg-id
3776.1116624678@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Preserving data after updates Berend Tober <btober@seaworthysys.com>
Re: Preserving data after updates Tom Lane <tgl@sss.pgh.pa.us>
Re: Preserving data after updates Berend Tober <btober@seaworthysys.com>
Re: Preserving data after updates Tom Lane <tgl@sss.pgh.pa.us>
Re: Preserving data after updates Berend Tober <btober@seaworthysys.com>
Re: Preserving data after updates Tom Lane <tgl@sss.pgh.pa.us>
Re: Preserving data after updates Berend Tober <btober@computer.org>
Re: Preserving data after updates Tom Lane <tgl@sss.pgh.pa.us>
Re: Preserving data after updates Berend Tober <btober@seaworthysys.com>
Inherited constraints and search paths (was Re: Preserving data after updates) Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Inherited constraints and search paths (was Re: Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] Inherited constraints and search paths (was Re: Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Inherited constraints and search paths Simon Riggs <simon@2ndquadrant.com>
Re: [HACKERS] Inherited constraints and search paths (was Re: Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Inherited constraints and search paths (was Berend Tober <btober@seaworthysys.com>
Re: [HACKERS] Inherited constraints and search paths (was Re: Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Inherited constraints and search paths (was Bruce Momjian <pgman@candle.pha.pa.us>
Re: [HACKERS] Inherited constraints and search paths (was Re: Berend Tober <btober@seaworthysys.com>
Berend Tober  writes:
> However, when I do a select from a view, which itself does a select from 
> a parent table, the query result does include the child table rows, 
> i.e., the SQL_INHERITANCE  setting is ignored in this situation. Should 
> the SQL_INHERITANCE  setting still rule?

I believe what matters is the sql_inheritance setting that was in force
when the view was created.  You should be able to replace the view and
get it to do what you want.

(Hmm ... which suggests that we have still another pg_dump issue,
because views will be dumped using ONLY or no marker, and so reloading
them into a server with SQL_INHERITANCE off would result in a change in
the view behavior.  Probably we need to put "SET SQL_INHERITANCE = ON"
into the standard prologue of pg_dump scripts.)

			regards, tom lane
В списке pgsql-general по дате отправления
От: Matthew Hixson
Дата:
Сообщение: GCC 4.0 on Mac OS X
От: Tom Lane
Дата:
Сообщение: Re: GCC 4.0 on Mac OS X
FAQ