Skip to content

Commit e11f307

Browse files
samimseihhackorum
authored andcommitted
vacuumlo: Document data loss risk for unrecognized column types.
Add a caution noting that large object references stored in columns of types not recognized by vacuumlo (such as text or bigint) will be treated as orphans and removed, resulting in data loss. Recommend the lo extension type to avoid this. Discussion: https://postgr.es/m/CALsgZNAM=AYK-9ZLR7Z0YLx6Lyx5aSrjjse3T+FmsJ=jTvfhDQ@mail.gmail.com
1 parent 61acbeb commit e11f307

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

doc/src/sgml/vacuumlo.sgml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -217,6 +217,19 @@
217217
containing these types. Matching entries are removed from the temporary table.
218218
The remaining entries in the temporary table identify orphaned LOs. These are removed.
219219
</para>
220+
221+
<caution>
222+
<para>
223+
Large object references stored in columns of other types, such as
224+
<type>text</type> or <type>bigint</type>, are not recognized by
225+
<application>vacuumlo</application> and will be treated as orphans,
226+
resulting in data loss. Using the <type>lo</type> type
227+
from the <xref linkend="lo"/> extension is recommended for columns that
228+
hold large object references, as it allows
229+
<application>vacuumlo</application> to find them and the
230+
<function>lo_manage</function> trigger to manage them.
231+
</para>
232+
</caution>
220233
</refsect1>
221234

222235
<refsect1>

0 commit comments

Comments
 (0)