rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/test/regress/expected/sanity_check.out

209 lines
3.6 KiB
Plaintext
Raw Normal View History

Update output to new psql conventions.
2000-01-05 18:31:08 +01:00
VACUUM;
--
-- sanity check, if we don't have indices the test will take years to
Tweak sanity_check regression test to display more tables (viz, those without indexes) but not to display temp tables. It's a bit hard to credit that sanity_check could get through a database-wide VACUUM while the preceding create_index test is still trying to clean up its temp tables ... but I see no other explanation for the current failure report from buildfarm member sponge.
2006-08-06 06:35:21 +02:00
-- complete. But skip TOAST relations (since they will have varying
-- names depending on the current OID counter) as well as temp tables
-- of other backends (to avoid timing-dependent behavior).
Update output to new psql conventions.
2000-01-05 18:31:08 +01:00
--
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
-- temporarily disable fancy output, so catalog changes create less diff noise
\a\t
Update output to new psql conventions.
2000-01-05 18:31:08 +01:00
SELECT relname, relhasindex
Tweak sanity_check regression test to display more tables (viz, those without indexes) but not to display temp tables. It's a bit hard to credit that sanity_check could get through a database-wide VACUUM while the preceding create_index test is still trying to clean up its temp tables ... but I see no other explanation for the current failure report from buildfarm member sponge.
2006-08-06 06:35:21 +02:00
FROM pg_class c LEFT JOIN pg_namespace n ON n.oid = relnamespace
Change the relkind for partitioned tables from 'P' to 'p'. Seven of the eight other relkind codes are lower-case, so it wasn't consistent for this one to be upper-case. Fix it while we still can. Historical notes: the reason for the lone exception, i.e. sequences being 'S', is that 's' was once used for "special" relations. Also, at one time the partitioned-tables patch used both 'P' and 'p', but that got changed, leaving only a surprising choice behind. This also fixes a couple little bits of technical debt, such as type_sanity.sql not knowing that 'm' is a legal value for relkind. Discussion: https://postgr.es/m/27899.1488909319@sss.pgh.pa.us
2017-03-10 19:15:47 +01:00
WHERE relkind IN ('r', 'p') AND (nspname ~ '^pg_temp_') IS NOT TRUE
More splits and cleanups...
1997-04-06 08:07:13 +02:00
ORDER BY relname;
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
a|f
a_star|f
abstime_tbl|f
aggtest|f
array_index_op_test|t
array_op_test|f
b|f
b_star|f
box_tbl|f
bprime|f
bt_f8_heap|t
bt_i4_heap|t
bt_name_heap|t
bt_txt_heap|t
c|f
c_star|f
char_tbl|f
check2_tbl|f
check_tbl|f
circle_tbl|t
city|f
copy_tbl|f
d|f
d_star|f
date_tbl|f
default_tbl|f
defaultexpr_tbl|f
dept|f
dupindexcols|t
e_star|f
emp|f
equipment_r|f
f_star|f
Fix broken dependency-mongering for index operator classes/families. For a long time, opclasscmds.c explained that "we do not create a dependency link to the AM [for an opclass or opfamily], because we don't currently support DROP ACCESS METHOD". Commit 473b93287040b200 invented DROP ACCESS METHOD, but it batted only 1 for 2 on adding the dependency links, and 0 for 2 on updating the comments about the topic. In passing, undo the same commit's entirely inappropriate decision to blow away an existing index as a side-effect of create_am.sql.
2016-04-14 05:33:31 +02:00
fast_emp4000|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
float4_tbl|f
float8_tbl|f
func_index_heap|t
hash_f8_heap|t
hash_i4_heap|t
hash_name_heap|t
hash_txt_heap|t
hobbies_r|f
ihighway|t
inet_tbl|f
inhf|f
inhx|t
insert_tbl|f
int2_tbl|f
int4_tbl|f
int8_tbl|f
interval_tbl|f
Fix two bugs in merging of inherited CHECK constraints. Historically, we've allowed users to add a CHECK constraint to a child table and then add an identical CHECK constraint to the parent. This results in "merging" the two constraints so that the pre-existing child constraint ends up with both conislocal = true and coninhcount > 0. However, if you tried to do it in the other order, you got a duplicate constraint error. This is problematic for pg_dump, which needs to issue separated ADD CONSTRAINT commands in some cases, but has no good way to ensure that the constraints will be added in the required order. And it's more than a bit arbitrary, too. The goal of complaining about duplicated ADD CONSTRAINT commands can be served if we reject the case of adding a constraint when the existing one already has conislocal = true; but if it has conislocal = false, let's just make the ADD CONSTRAINT set conislocal = true. In this way, either order of adding the constraints has the same end result. Another problem was that the code allowed creation of a parent constraint marked convalidated that is merged with a child constraint that is !convalidated. In this case, an inheritance scan of the parent table could emit some rows violating the constraint condition, which would be an unexpected result given the marking of the parent constraint as validated. Hence, forbid merging of constraints in this case. (Note: valid child and not-valid parent seems fine, so continue to allow that.) Per report from Benedikt Grundmann. Back-patch to 9.2 where we introduced possibly-not-valid check constraints. The second bug obviously doesn't apply before that, and I think the first doesn't either, because pg_dump only gets into this situation when dealing with not-valid constraints. Report: <CADbMkNPT-Jz5PRSQ4RbUASYAjocV_KHUWapR%2Bg8fNvhUAyRpxA%40mail.gmail.com> Discussion: <22108.1475874586@sss.pgh.pa.us>
2016-10-09 01:29:27 +02:00
invalid_check_con|f
invalid_check_con_child|f
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
iportaltest|f
kd_point_tbl|t
line_tbl|f
log_table|f
lseg_tbl|f
main_table|f
Give partitioned table "p" in regression tests a less generic name. And don't drop it, so that we improve the coverage of the pg_upgrade regression tests. Amit Langote, per a gripe from Tom Lane Discussion: http://postgr.es/m/9071.1488863082@sss.pgh.pa.us
2017-03-07 17:32:33 +01:00
mlparted|f
mlparted1|f
mlparted11|f
mlparted12|f
mlparted2|f
mlparted3|f
mlparted4|f
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
money_data|f
num_data|f
num_exp_add|t
num_exp_div|t
num_exp_ln|t
num_exp_log10|t
num_exp_mul|t
num_exp_power_10_ln|t
num_exp_sqrt|t
num_exp_sub|t
num_input_test|f
num_result|f
onek|t
onek2|t
path_tbl|f
person|f
pg_aggregate|t
pg_am|t
pg_amop|t
pg_amproc|t
pg_attrdef|t
pg_attribute|t
pg_auth_members|t
pg_authid|t
pg_cast|t
pg_class|t
pg_collation|t
pg_constraint|t
pg_conversion|t
pg_database|t
pg_db_role_setting|t
pg_default_acl|t
pg_depend|t
pg_description|t
pg_enum|t
pg_event_trigger|t
pg_extension|t
pg_foreign_data_wrapper|t
pg_foreign_server|t
pg_foreign_table|t
pg_index|t
pg_inherits|t
Add new catalog called pg_init_privs This new catalog holds the privileges which the system was initialized with at initdb time, along with any permissions set by extensions at CREATE EXTENSION time. This allows pg_dump (and any other similar use-cases) to detect when the privileges set on initdb-created or extension-created objects have been changed from what they were set to at initdb/extension-creation time and handle those changes appropriately. Reviews by Alexander Korotkov, Jose Luis Tallon
2016-04-07 03:45:32 +02:00
pg_init_privs|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_language|t
pg_largeobject|t
pg_largeobject_metadata|t
pg_namespace|t
pg_opclass|t
pg_operator|t
pg_opfamily|t
Implement table partitioning. Table partitioning is like table inheritance and reuses much of the existing infrastructure, but there are some important differences. The parent is called a partitioned table and is always empty; it may not have indexes or non-inherited constraints, since those make no sense for a relation with no data of its own. The children are called partitions and contain all of the actual data. Each partition has an implicit partitioning constraint. Multiple inheritance is not allowed, and partitioning and inheritance can't be mixed. Partitions can't have extra columns and may not allow nulls unless the parent does. Tuples inserted into the parent are automatically routed to the correct partition, so tuple-routing ON INSERT triggers are not needed. Tuple routing isn't yet supported for partitions which are foreign tables, and it doesn't handle updates that cross partition boundaries. Currently, tables can be range-partitioned or list-partitioned. List partitioning is limited to a single column, but range partitioning can involve multiple columns. A partitioning "column" can be an expression. Because table partitioning is less general than table inheritance, it is hoped that it will be easier to reason about properties of partitions, and therefore that this will serve as a better foundation for a variety of possible optimizations, including query planner optimizations. The tuple routing based which this patch does based on the implicit partitioning constraints is an example of this, but it seems likely that many other useful optimizations are also possible. Amit Langote, reviewed and tested by Robert Haas, Ashutosh Bapat, Amit Kapila, Rajkumar Raghuwanshi, Corey Huinker, Jaime Casanova, Rushabh Lathia, Erik Rijkers, among others. Minor revisions by me.
2016-12-07 19:17:43 +01:00
pg_partitioned_table|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_pltemplate|t
Rename pg_rowsecurity -> pg_policy and other fixes As pointed out by Robert, we should really have named pg_rowsecurity pg_policy, as the objects stored in that catalog are policies. This patch fixes that and updates the column names to start with 'pol' to match the new catalog name. The security consideration for COPY with row level security, also pointed out by Robert, has also been addressed by remembering and re-checking the OID of the relation initially referenced during COPY processing, to make sure it hasn't changed under us by the time we finish planning out the query which has been built. Robert and Alvaro also commented on missing OCLASS and OBJECT entries for POLICY (formerly ROWSECURITY or POLICY, depending) in various places. This patch fixes that too, which also happens to add the ability to COMMENT on policies. In passing, attempt to improve the consistency of messages, comments, and documentation as well. This removes various incarnations of 'row-security', 'row-level security', 'Row-security', etc, in favor of 'policy', 'row level security' or 'row_security' as appropriate. Happy Thanksgiving!
2014-11-27 07:06:36 +01:00
pg_policy|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_proc|t
Logical replication - Add PUBLICATION catalogs and DDL - Add SUBSCRIPTION catalog and DDL - Define logical replication protocol and output plugin - Add logical replication workers From: Petr Jelinek <petr@2ndquadrant.com> Reviewed-by: Steve Singer <steve@ssinger.info> Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Erik Rijkers <er@xs4all.nl> Reviewed-by: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-01-19 18:00:00 +01:00
pg_publication|t
pg_publication_rel|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_range|t
Introduce replication progress tracking infrastructure. When implementing a replication solution ontop of logical decoding, two related problems exist: * How to safely keep track of replication progress * How to change replication behavior, based on the origin of a row; e.g. to avoid loops in bi-directional replication setups The solution to these problems, as implemented here, consist out of three parts: 1) 'replication origins', which identify nodes in a replication setup. 2) 'replication progress tracking', which remembers, for each replication origin, how far replay has progressed in a efficient and crash safe manner. 3) The ability to filter out changes performed on the behest of a replication origin during logical decoding; this allows complex replication topologies. E.g. by filtering all replayed changes out. Most of this could also be implemented in "userspace", e.g. by inserting additional rows contain origin information, but that ends up being much less efficient and more complicated. We don't want to require various replication solutions to reimplement logic for this independently. The infrastructure is intended to be generic enough to be reusable. This infrastructure also replaces the 'nodeid' infrastructure of commit timestamps. It is intended to provide all the former capabilities, except that there's only 2^16 different origins; but now they integrate with logical decoding. Additionally more functionality is accessible via SQL. Since the commit timestamp infrastructure has also been introduced in 9.5 (commit 73c986add) changing the API is not a problem. For now the number of origins for which the replication progress can be tracked simultaneously is determined by the max_replication_slots GUC. That GUC is not a perfect match to configure this, but there doesn't seem to be sufficient reason to introduce a separate new one. Bumps both catversion and wal page magic. Author: Andres Freund, with contributions from Petr Jelinek and Craig Ringer Reviewed-By: Heikki Linnakangas, Petr Jelinek, Robert Haas, Steve Singer Discussion: 20150216002155.GI15326@awork2.anarazel.de, 20140923182422.GA15776@alap3.anarazel.de, 20131114172632.GE7522@alap2.anarazel.de
2015-04-29 19:30:53 +02:00
pg_replication_origin|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_rewrite|t
pg_seclabel|t
Add pg_sequence system catalog Move sequence metadata (start, increment, etc.) into a proper system catalog instead of storing it in the sequence heap object. This separates the metadata from the sequence data. Sequence metadata is now operated on transactionally by DDL commands, whereas previously rollbacks of sequence-related DDL commands would be ignored. Reviewed-by: Andreas Karlsson <andreas@proxel.se>
2016-12-20 18:00:00 +01:00
pg_sequence|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_shdepend|t
pg_shdescription|t
pg_shseclabel|t
pg_statistic|t
Logical replication - Add PUBLICATION catalogs and DDL - Add SUBSCRIPTION catalog and DDL - Define logical replication protocol and output plugin - Add logical replication workers From: Petr Jelinek <petr@2ndquadrant.com> Reviewed-by: Steve Singer <steve@ssinger.info> Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Erik Rijkers <er@xs4all.nl> Reviewed-by: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-01-19 18:00:00 +01:00
pg_subscription|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_tablespace|t
Add transforms feature This provides a mechanism for specifying conversions between SQL data types and procedural languages. As examples, there are transforms for hstore and ltree for PL/Perl and PL/Python. reviews by Pavel Stěhule and Andres Freund
2015-04-26 16:33:14 +02:00
pg_transform|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
pg_trigger|t
pg_ts_config|t
pg_ts_config_map|t
pg_ts_dict|t
pg_ts_parser|t
pg_ts_template|t
pg_type|t
pg_user_mapping|t
point_tbl|t
polygon_tbl|t
Fix support for some operators (&<, &>, $<|, |&>) in box operator class of SP-GiST. Bug exists since initial commit of box opclass for SP-GiST, so backpath to 9.6 Author: Nikita Glukhov with minor editorization of tests by me Reviewed-by: Kyotaro Horiguchi, Anastasia Lubennikova https://commitfest.postgresql.org/13/981/
2017-03-21 14:23:10 +01:00
quad_box_tbl|t
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
quad_point_tbl|t
radix_text_tbl|t
ramp|f
real_city|f
reltime_tbl|f
road|t
shighway|t
slow_emp4000|f
sql_features|f
sql_implementation_info|f
sql_languages|f
sql_packages|f
sql_parts|f
sql_sizing|f
sql_sizing_profiles|f
stud_emp|f
student|f
tenk1|t
tenk2|t
test_range_excl|t
test_range_gist|t
test_range_spgist|t
test_tsvector|f
Do jsonb regression test input in the conventional way. This should make the buildfarm happier.
2014-03-24 01:18:06 +01:00
testjsonb|f
Use unaligned output in selected regression queries to reduce diff noise. The rules regression test prints all known views and rules, which is a set that changes regularly. Previously, a change in one rule would frequently lead to whitespace changes across the entire output of this query, which is painful to verify and causes undesirable conflicts between unrelated patch sets. Use \a mode to improve matters. Also use \t mode to suppress the total-rows count, which was also a source of unnecessary patch conflicts. Likewise modify the output mode for the list of indexed tables generated in sanity_check.sql. There might be other places where we should use this idea, but these are the ones that have caused the most problems. Andres Freund
2013-10-26 17:24:04 +02:00
text_tbl|f
time_tbl|f
timestamp_tbl|f
timestamptz_tbl|f
timetz_tbl|f
tinterval_tbl|f
varchar_tbl|f
-- restore normal output mode
\a\t
Add a sanity check to make sure that all system catalogs that have OIDs also have a unique index on OID.
2002-08-10 17:54:04 +02:00
--
-- another sanity check: every system catalog that has OIDs should have
-- a unique index on OID. This ensures that the OIDs will be unique,
-- even after the OID counter wraps around.
-- We exclude non-system tables from the check by looking at nspname.
--
SELECT relname, nspname
FROM pg_class c LEFT JOIN pg_namespace n ON n.oid = relnamespace
WHERE relhasoids
AND ((nspname ~ '^pg_') IS NOT FALSE)
AND NOT EXISTS (SELECT 1 FROM pg_index i WHERE indrelid = c.oid
Support deferrable uniqueness constraints. The current implementation fires an AFTER ROW trigger for each tuple that looks like it might be non-unique according to the index contents at the time of insertion. This works well as long as there aren't many conflicts, but won't scale to massive unique-key reassignments. Improving that case is a TODO item. Dean Rasheed
2009-07-29 22:56:21 +02:00
AND indkey[0] = -2 AND indnatts = 1
AND indisunique AND indimmediate);
Add a sanity check to make sure that all system catalogs that have OIDs also have a unique index on OID.
2002-08-10 17:54:04 +02:00
relname | nspname
---------+---------
(0 rows)