← Back to branch summary

~ubuntu-branches/ubuntu/trusty/postgresql-8.4/trusty

« back to all changes in this revision

Viewing changes to src/backend/catalog/pg_inherits.c

  • Committer: Bazaar Package Importer
  • Author(s): Martin Pitt
  • Date: 2009-07-11 16:59:35 UTC
  • mfrom: (5.1.1 karmic)
  • Revision ID: james.westby@ubuntu.com-20090711165935-jfwin6gfrxf0gfsi
Tags: 8.4.0-2
http://bugs.debian.org/536139
* debian/libpq-dev.install: Ship catalog/genbki.h. (Closes: #536139)
* debian/rules: Drop --enable-cassert for final release.

Show diffs side-by-side

added added

removed removed

Lines of Context:
src/backend/catalog/pg_inherits.c
13
13
 *
14
14
 *
15
15
 * IDENTIFICATION
16
 
 *        $PostgreSQL: pgsql/src/backend/catalog/pg_inherits.c,v 1.2 2009/05/12 03:11:01 tgl Exp $
 
16
 *        $PostgreSQL: pgsql/src/backend/catalog/pg_inherits.c,v 1.3 2009/06/11 14:48:55 momjian Exp $
17
17
 *
18
18
 *-------------------------------------------------------------------------
19
19
 */
82
82
 
83
83
                        /*
84
84
                         * Now that we have the lock, double-check to see if the relation
85
 
                         * really exists or not.  If not, assume it was dropped while
86
 
                         * we waited to acquire lock, and ignore it.
 
85
                         * really exists or not.  If not, assume it was dropped while we
 
86
                         * waited to acquire lock, and ignore it.
87
87
                         */
88
88
                        if (!SearchSysCacheExists(RELOID,
89
89
                                                                          ObjectIdGetDatum(inhrelid),
235
235
                HeapTuple       inhtup;
236
236
 
237
237
                /*
238
 
                 * If we've seen this relid already, skip it.  This avoids extra
239
 
                 * work in multiple-inheritance scenarios, and also protects us
240
 
                 * from an infinite loop in case there is a cycle in pg_inherits
241
 
                 * (though theoretically that shouldn't happen).
 
238
                 * If we've seen this relid already, skip it.  This avoids extra work
 
239
                 * in multiple-inheritance scenarios, and also protects us from an
 
240
                 * infinite loop in case there is a cycle in pg_inherits (though
 
241
                 * theoretically that shouldn't happen).
242
242
                 */
243
243
                if (list_member_oid(visited, this_relid))
244
244
                        continue;