1996-07-09 08:22:35 +02:00
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
1999-02-14 00:22:53 +01:00
|
|
|
* rewriteSupport.c
|
1996-07-09 08:22:35 +02:00
|
|
|
*
|
|
|
|
|
*
|
2021-01-02 19:06:25 +01:00
|
|
|
* Portions Copyright (c) 1996-2021, PostgreSQL Global Development Group
|
2000-01-26 06:58:53 +01:00
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
1996-07-09 08:22:35 +02:00
|
|
|
*
|
|
|
|
|
*
|
|
|
|
|
* IDENTIFICATION
|
2010-09-20 22:08:53 +02:00
|
|
|
* src/backend/rewrite/rewriteSupport.c
|
1996-07-09 08:22:35 +02:00
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
#include "postgres.h"
|
1998-04-27 06:08:07 +02:00
|
|
|
|
2012-08-30 22:15:44 +02:00
|
|
|
#include "access/htup_details.h"
|
2019-01-21 19:18:20 +01:00
|
|
|
#include "access/table.h"
|
1998-04-27 06:08:07 +02:00
|
|
|
#include "catalog/indexing.h"
|
2010-08-05 17:25:36 +02:00
|
|
|
#include "catalog/pg_rewrite.h"
|
1999-07-16 07:00:38 +02:00
|
|
|
#include "rewrite/rewriteSupport.h"
|
2010-08-05 17:25:36 +02:00
|
|
|
#include "utils/fmgroids.h"
|
2002-07-12 20:43:19 +02:00
|
|
|
#include "utils/inval.h"
|
2010-08-05 17:25:36 +02:00
|
|
|
#include "utils/lsyscache.h"
|
|
|
|
|
#include "utils/rel.h"
|
1999-07-16 05:14:30 +02:00
|
|
|
#include "utils/syscache.h"
|
1998-04-27 06:08:07 +02:00
|
|
|
|
2001-08-12 23:35:19 +02:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Is there a rule by the given name?
|
|
|
|
|
*/
|
2000-11-16 23:30:52 +01:00
|
|
|
bool
|
2002-04-18 22:01:11 +02:00
|
|
|
IsDefinedRewriteRule(Oid owningRel, const char *ruleName)
|
1996-07-09 08:22:35 +02:00
|
|
|
{
|
2010-02-14 19:42:19 +01:00
|
|
|
return SearchSysCacheExists2(RULERELNAME,
|
|
|
|
|
ObjectIdGetDatum(owningRel),
|
|
|
|
|
PointerGetDatum(ruleName));
|
1996-07-09 08:22:35 +02:00
|
|
|
}
|
|
|
|
|
|
2001-08-12 23:35:19 +02:00
|
|
|
|
2000-06-30 09:04:23 +02:00
|
|
|
/*
|
2000-09-29 20:21:41 +02:00
|
|
|
* SetRelationRuleStatus
|
2013-03-04 01:05:47 +01:00
|
|
|
* Set the value of the relation's relhasrules field in pg_class.
|
2000-06-30 09:04:23 +02:00
|
|
|
*
|
2000-09-29 20:21:41 +02:00
|
|
|
* NOTE: caller must be holding an appropriate lock on the relation.
|
2000-06-30 09:04:23 +02:00
|
|
|
*
|
|
|
|
|
* NOTE: an important side-effect of this operation is that an SI invalidation
|
|
|
|
|
* message is sent out to all backends --- including me --- causing relcache
|
|
|
|
|
* entries to be flushed or updated with the new set of rules for the table.
|
2002-07-12 20:43:19 +02:00
|
|
|
* This must happen even if we find that no change is needed in the pg_class
|
|
|
|
|
* row.
|
2000-06-30 09:04:23 +02:00
|
|
|
*/
|
|
|
|
|
void
|
2013-03-04 01:05:47 +01:00
|
|
|
SetRelationRuleStatus(Oid relationId, bool relHasRules)
|
1996-07-09 08:22:35 +02:00
|
|
|
{
|
|
|
|
|
Relation relationRelation;
|
|
|
|
|
HeapTuple tuple;
|
2002-07-12 20:43:19 +02:00
|
|
|
Form_pg_class classForm;
|
1997-09-07 07:04:48 +02:00
|
|
|
|
1996-07-09 08:22:35 +02:00
|
|
|
/*
|
2000-06-30 09:04:23 +02:00
|
|
|
* Find the tuple to update in pg_class, using syscache for the lookup.
|
1996-07-09 08:22:35 +02:00
|
|
|
*/
|
2019-01-21 19:32:19 +01:00
|
|
|
relationRelation = table_open(RelationRelationId, RowExclusiveLock);
|
2010-02-14 19:42:19 +01:00
|
|
|
tuple = SearchSysCacheCopy1(RELOID, ObjectIdGetDatum(relationId));
|
2000-11-16 23:30:52 +01:00
|
|
|
if (!HeapTupleIsValid(tuple))
|
2003-07-25 02:01:09 +02:00
|
|
|
elog(ERROR, "cache lookup failed for relation %u", relationId);
|
2002-07-12 20:43:19 +02:00
|
|
|
classForm = (Form_pg_class) GETSTRUCT(tuple);
|
1997-09-07 07:04:48 +02:00
|
|
|
|
2013-03-04 01:05:47 +01:00
|
|
|
if (classForm->relhasrules != relHasRules)
|
2002-07-12 20:43:19 +02:00
|
|
|
{
|
|
|
|
|
/* Do the update */
|
|
|
|
|
classForm->relhasrules = relHasRules;
|
2000-09-29 20:21:41 +02:00
|
|
|
|
2017-01-31 22:42:24 +01:00
|
|
|
CatalogTupleUpdate(relationRelation, &tuple->t_self, tuple);
|
2002-07-12 20:43:19 +02:00
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
{
|
|
|
|
|
/* no need to change tuple, but force relcache rebuild anyway */
|
2004-02-10 02:55:27 +01:00
|
|
|
CacheInvalidateRelcacheByTuple(tuple);
|
2002-07-12 20:43:19 +02:00
|
|
|
}
|
1997-09-07 07:04:48 +02:00
|
|
|
|
1999-12-16 23:20:03 +01:00
|
|
|
heap_freetuple(tuple);
|
2019-01-21 19:32:19 +01:00
|
|
|
table_close(relationRelation, RowExclusiveLock);
|
1996-07-09 08:22:35 +02:00
|
|
|
}
|
2010-08-05 17:25:36 +02:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Find rule oid.
|
|
|
|
|
*
|
|
|
|
|
* If missing_ok is false, throw an error if rule name not found. If
|
|
|
|
|
* true, just return InvalidOid.
|
|
|
|
|
*/
|
|
|
|
|
Oid
|
|
|
|
|
get_rewrite_oid(Oid relid, const char *rulename, bool missing_ok)
|
|
|
|
|
{
|
|
|
|
|
HeapTuple tuple;
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
Form_pg_rewrite ruleform;
|
2010-08-05 17:25:36 +02:00
|
|
|
Oid ruleoid;
|
|
|
|
|
|
|
|
|
|
/* Find the rule's pg_rewrite tuple, get its OID */
|
|
|
|
|
tuple = SearchSysCache2(RULERELNAME,
|
|
|
|
|
ObjectIdGetDatum(relid),
|
|
|
|
|
PointerGetDatum(rulename));
|
|
|
|
|
if (!HeapTupleIsValid(tuple))
|
|
|
|
|
{
|
|
|
|
|
if (missing_ok)
|
|
|
|
|
return InvalidOid;
|
|
|
|
|
ereport(ERROR,
|
|
|
|
|
(errcode(ERRCODE_UNDEFINED_OBJECT),
|
|
|
|
|
errmsg("rule \"%s\" for relation \"%s\" does not exist",
|
|
|
|
|
rulename, get_rel_name(relid))));
|
|
|
|
|
}
|
Remove WITH OIDS support, change oid catalog column visibility.
Previously tables declared WITH OIDS, including a significant fraction
of the catalog tables, stored the oid column not as a normal column,
but as part of the tuple header.
This special column was not shown by default, which was somewhat odd,
as it's often (consider e.g. pg_class.oid) one of the more important
parts of a row. Neither pg_dump nor COPY included the contents of the
oid column by default.
The fact that the oid column was not an ordinary column necessitated a
significant amount of special case code to support oid columns. That
already was painful for the existing, but upcoming work aiming to make
table storage pluggable, would have required expanding and duplicating
that "specialness" significantly.
WITH OIDS has been deprecated since 2005 (commit ff02d0a05280e0).
Remove it.
Removing includes:
- CREATE TABLE and ALTER TABLE syntax for declaring the table to be
WITH OIDS has been removed (WITH (oids[ = true]) will error out)
- pg_dump does not support dumping tables declared WITH OIDS and will
issue a warning when dumping one (and ignore the oid column).
- restoring an pg_dump archive with pg_restore will warn when
restoring a table with oid contents (and ignore the oid column)
- COPY will refuse to load binary dump that includes oids.
- pg_upgrade will error out when encountering tables declared WITH
OIDS, they have to be altered to remove the oid column first.
- Functionality to access the oid of the last inserted row (like
plpgsql's RESULT_OID, spi's SPI_lastoid, ...) has been removed.
The syntax for declaring a table WITHOUT OIDS (or WITH (oids = false)
for CREATE TABLE) is still supported. While that requires a bit of
support code, it seems unnecessary to break applications / dumps that
do not use oids, and are explicit about not using them.
The biggest user of WITH OID columns was postgres' catalog. This
commit changes all 'magic' oid columns to be columns that are normally
declared and stored. To reduce unnecessary query breakage all the
newly added columns are still named 'oid', even if a table's column
naming scheme would indicate 'reloid' or such. This obviously
requires adapting a lot code, mostly replacing oid access via
HeapTupleGetOid() with access to the underlying Form_pg_*->oid column.
The bootstrap process now assigns oids for all oid columns in
genbki.pl that do not have an explicit value (starting at the largest
oid previously used), only oids assigned later by oids will be above
FirstBootstrapObjectId. As the oid column now is a normal column the
special bootstrap syntax for oids has been removed.
Oids are not automatically assigned during insertion anymore, all
backend code explicitly assigns oids with GetNewOidWithIndex(). For
the rare case that insertions into the catalog via SQL are called for
the new pg_nextoid() function can be used (which only works on catalog
tables).
The fact that oid columns on system tables are now normal columns
means that they will be included in the set of columns expanded
by * (i.e. SELECT * FROM pg_class will now include the table's oid,
previously it did not). It'd not technically be hard to hide oid
column by default, but that'd mean confusing behavior would either
have to be carried forward forever, or it'd cause breakage down the
line.
While it's not unlikely that further adjustments are needed, the
scope/invasiveness of the patch makes it worthwhile to get merge this
now. It's painful to maintain externally, too complicated to commit
after the code code freeze, and a dependency of a number of other
patches.
Catversion bump, for obvious reasons.
Author: Andres Freund, with contributions by John Naylor
Discussion: https://postgr.es/m/20180930034810.ywp2c7awz7opzcfr@alap3.anarazel.de
2018-11-21 00:36:57 +01:00
|
|
|
ruleform = (Form_pg_rewrite) GETSTRUCT(tuple);
|
|
|
|
|
Assert(relid == ruleform->ev_class);
|
|
|
|
|
ruleoid = ruleform->oid;
|
2010-08-05 17:25:36 +02:00
|
|
|
ReleaseSysCache(tuple);
|
|
|
|
|
return ruleoid;
|
|
|
|
|
}
|
