mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-16 03:40:37 +02:00
b0a55e4329
We have been using the term RelFileNode to refer to either (1) the integer that is used to name the sequence of files for a certain relation within the directory set aside for that tablespace/database combination; or (2) that value plus the OIDs of the tablespace and database; or occasionally (3) the whole series of files created for a relation based on those values. Using the same name for more than one thing is confusing. Replace RelFileNode with RelFileNumber when we're talking about just the single number, i.e. (1) from above, and with RelFileLocator when we're talking about all the things that are needed to locate a relation's files on disk, i.e. (2) from above. In the places where we refer to (3) as a relfilenode, instead refer to "relation storage". Since there is a ton of SQL code in the world that knows about pg_class.relfilenode, don't change the name of that column, or of other SQL-facing things that derive their name from it. On the other hand, do adjust closely-related internal terminology. For example, the structure member names dbNode and spcNode appear to be derived from the fact that the structure itself was called RelFileNode, so change those to dbOid and spcOid. Likewise, various variables with names like rnode and relnode get renamed appropriately, according to how they're being used in context. Hopefully, this is clearer than before. It is also preparation for future patches that intend to widen the relfilenumber fields from its current width of 32 bits. Variables that store a relfilenumber are now declared as type RelFileNumber rather than type Oid; right now, these are the same, but that can now more easily be changed. Dilip Kumar, per an idea from me. Reviewed also by Andres Freund. I fixed some whitespace issues, changed a couple of words in a comment, and made one other minor correction. Discussion: http://postgr.es/m/CA+TgmoamOtXbVAQf9hWFzonUo6bhhjS6toZQd7HZ-pmojtAmag@mail.gmail.com Discussion: http://postgr.es/m/CA+Tgmobp7+7kmi4gkq7Y+4AM9fTvL+O1oQ4-5gFTT+6Ng-dQ=g@mail.gmail.com Discussion: http://postgr.es/m/CAFiTN-vTe79M8uDH1yprOU64MNFE+R3ODRuA+JWf27JbhY4hJw@mail.gmail.com
82 lines
2.4 KiB
C
82 lines
2.4 KiB
C
/*-------------------------------------------------------------------------
|
|
*
|
|
* postgres_ext.h
|
|
*
|
|
* This file contains declarations of things that are visible everywhere
|
|
* in PostgreSQL *and* are visible to clients of frontend interface libraries.
|
|
* For example, the Oid type is part of the API of libpq and other libraries.
|
|
*
|
|
* Declarations which are specific to a particular interface should
|
|
* go in the header file for that interface (such as libpq-fe.h). This
|
|
* file is only for fundamental Postgres declarations.
|
|
*
|
|
* User-written C functions don't count as "external to Postgres."
|
|
* Those function much as local modifications to the backend itself, and
|
|
* use header files that are otherwise internal to Postgres to interface
|
|
* with the backend.
|
|
*
|
|
* src/include/postgres_ext.h
|
|
*
|
|
*-------------------------------------------------------------------------
|
|
*/
|
|
|
|
#ifndef POSTGRES_EXT_H
|
|
#define POSTGRES_EXT_H
|
|
|
|
#include "pg_config_ext.h"
|
|
|
|
/*
|
|
* Object ID is a fundamental type in Postgres.
|
|
*/
|
|
typedef unsigned int Oid;
|
|
|
|
#ifdef __cplusplus
|
|
#define InvalidOid (Oid(0))
|
|
#else
|
|
#define InvalidOid ((Oid) 0)
|
|
#endif
|
|
|
|
#define OID_MAX UINT_MAX
|
|
/* you will need to include <limits.h> to use the above #define */
|
|
|
|
#define atooid(x) ((Oid) strtoul((x), NULL, 10))
|
|
/* the above needs <stdlib.h> */
|
|
|
|
|
|
/* Define a signed 64-bit integer type for use in client API declarations. */
|
|
typedef PG_INT64_TYPE pg_int64;
|
|
|
|
/*
|
|
* RelFileNumber data type identifies the specific relation file name.
|
|
*/
|
|
typedef Oid RelFileNumber;
|
|
#define InvalidRelFileNumber ((RelFileNumber) InvalidOid)
|
|
#define RelFileNumberIsValid(relnumber) \
|
|
((bool) ((relnumber) != InvalidRelFileNumber))
|
|
|
|
/*
|
|
* Identifiers of error message fields. Kept here to keep common
|
|
* between frontend and backend, and also to export them to libpq
|
|
* applications.
|
|
*/
|
|
#define PG_DIAG_SEVERITY 'S'
|
|
#define PG_DIAG_SEVERITY_NONLOCALIZED 'V'
|
|
#define PG_DIAG_SQLSTATE 'C'
|
|
#define PG_DIAG_MESSAGE_PRIMARY 'M'
|
|
#define PG_DIAG_MESSAGE_DETAIL 'D'
|
|
#define PG_DIAG_MESSAGE_HINT 'H'
|
|
#define PG_DIAG_STATEMENT_POSITION 'P'
|
|
#define PG_DIAG_INTERNAL_POSITION 'p'
|
|
#define PG_DIAG_INTERNAL_QUERY 'q'
|
|
#define PG_DIAG_CONTEXT 'W'
|
|
#define PG_DIAG_SCHEMA_NAME 's'
|
|
#define PG_DIAG_TABLE_NAME 't'
|
|
#define PG_DIAG_COLUMN_NAME 'c'
|
|
#define PG_DIAG_DATATYPE_NAME 'd'
|
|
#define PG_DIAG_CONSTRAINT_NAME 'n'
|
|
#define PG_DIAG_SOURCE_FILE 'F'
|
|
#define PG_DIAG_SOURCE_LINE 'L'
|
|
#define PG_DIAG_SOURCE_FUNCTION 'R'
|
|
|
|
#endif /* POSTGRES_EXT_H */
|