From 84f910a7076e09e551bf69e0972473ec15d33c79 Mon Sep 17 00:00:00 2001
From: Itagaki Takahiro
Date: Mon, 14 Dec 2009 00:39:11 +0000
Subject: Additional fixes for large object access control. Use
 pg_largeobject_metadata.oid instead of pg_largeobject.loid to enumerate
 existing large objects in pg_dump, pg_restore, and contrib modules.

---
 contrib/lo/lo_test.sql | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'contrib/lo')

diff --git a/contrib/lo/lo_test.sql b/contrib/lo/lo_test.sql
index e22a8889b31..73022b2535a 100644
--- a/contrib/lo/lo_test.sql
+++ b/contrib/lo/lo_test.sql
@@ -1,4 +1,4 @@
-/* $PostgreSQL: pgsql/contrib/lo/lo_test.sql,v 1.5 2007/11/13 04:24:28 momjian Exp $ */
+/* $PostgreSQL: pgsql/contrib/lo/lo_test.sql,v 1.6 2009/12/14 00:39:10 itagaki Exp $ */
 
 -- Adjust this setting to control where the objects get created.
 SET search_path = public;
@@ -12,7 +12,7 @@ SET search_path = public;
 --
 
 -- Check what is in pg_largeobject
-SELECT count(DISTINCT loid) FROM pg_largeobject;
+SELECT count(oid) FROM pg_largeobject_metadata;
 
 -- ignore any errors here - simply drop the table if it already exists
 DROP TABLE a;
@@ -74,6 +74,6 @@ DELETE FROM a;
 DROP TABLE a;
 
 -- Check what is in pg_largeobject ... if different from original, trouble
-SELECT count(DISTINCT loid) FROM pg_largeobject;
+SELECT count(oid) FROM pg_largeobject_metadata;
 
 -- end of tests
-- 
cgit v1.2.3