mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-14 00:09:35 +02:00
bcac23de73
An extensible node is always tagged T_Extensible, but the extnodename field identifies it more specifically; it may also include arbitrary private data. Extensible nodes can be copied, tested for equality, serialized, and deserialized, but the core system doesn't know anything about them otherwise. Some extensions may find it useful to include these nodes in fdw_private or custom_private lists in lieu of arm-wrestling their data into a format that the core code can understand. Along the way, so as not to burden the authors of such extensible node types too much, expose the functions for writing serialized tokens, and for serializing and deserializing bitmapsets. KaiGai Kohei, per a design suggested by me. Reviewed by Andres Freund and by me, and further edited by me.
20 lines
573 B
Makefile
20 lines
573 B
Makefile
#-------------------------------------------------------------------------
|
|
#
|
|
# Makefile--
|
|
# Makefile for backend/nodes
|
|
#
|
|
# IDENTIFICATION
|
|
# src/backend/nodes/Makefile
|
|
#
|
|
#-------------------------------------------------------------------------
|
|
|
|
subdir = src/backend/nodes
|
|
top_builddir = ../../..
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
OBJS = nodeFuncs.o nodes.o list.o bitmapset.o tidbitmap.o \
|
|
copyfuncs.o equalfuncs.o extensible.o makefuncs.o \
|
|
outfuncs.o readfuncs.o print.o read.o params.o value.o
|
|
|
|
include $(top_srcdir)/src/backend/common.mk
|