Michael Paquier 55f4802785 Prevent write operations on large objects in read-only transactions ... Attempting such an operation would already fail, but in various and confusing ways. For example, while in recovery, some elog() messages would be reported, but these should never be user-facing. This commit restricts any write operations done on large objects in a read-only context, so as the errors generated are more user-friendly. This is per the discussion done with Tom Lane and Robert Haas. Some regression tests are added to check the case of all the SQL functions working on large objects (including an update of the test's alternate output). Author: Yugo Nagata Discussion: https://postgr.es/m/20220527153028.61a4608f66abcd026fd3806f@sraoss.co.jp		2022-07-04 15:48:52 +09:00
..
sgml	Prevent write operations on large objects in read-only transactions	2022-07-04 15:48:52 +09:00
Makefile	Remove maintainer-check target, fold into normal build	2013-10-10 20:11:56 -04:00