slightly confusing "contents of views"

Started by jian he12 days ago2 messagesdocs
Jump to latest
#1jian he
jian.universality@gmail.com

https://www.postgresql.org/docs/devel/app-pgdump.html
<<>>
As well as tables, this option can be used to dump the definition of
matching views, materialized views, foreign tables, and sequences. It
will not dump the contents of views or materialized views, and the
contents of foreign tables will only be dumped if the corresponding
foreign server is specified with --include-foreign-data.
<<>>

Views don't have content, the preceding sentence already mentioned we
will dump the definition of views.

So we can change
``It will not dump the contents of views or materialized views,``
to
``It will not dump the contents of materialized views,``

#2Peter Eisentraut
peter_e@gmx.net
In reply to: jian he (#1)
Re: slightly confusing "contents of views"

On 12.08.26 06:39, jian he wrote:

https://www.postgresql.org/docs/devel/app-pgdump.html
<<>>
As well as tables, this option can be used to dump the definition of
matching views, materialized views, foreign tables, and sequences. It
will not dump the contents of views or materialized views, and the
contents of foreign tables will only be dumped if the corresponding
foreign server is specified with --include-foreign-data.
<<>>

Views don't have content, the preceding sentence already mentioned we
will dump the definition of views.

So we can change
``It will not dump the contents of views or materialized views,``
to
``It will not dump the contents of materialized views,``

Views have content in a way. It is computed on the fly. One could
imagine a pg_dump feature that dumps out view content like a table (with
COPY or INSERT commands) and allows restoring it. I think it's not
redundant to clarify that this does not happen.