Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
57da4cca
Commit
57da4cca
authored
Dec 03, 2007
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve partitioning example, per Itagaki Takahiro.
parent
531f5868
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
6 deletions
+16
-6
doc/src/sgml/ddl.sgml
doc/src/sgml/ddl.sgml
+16
-6
No files found.
doc/src/sgml/ddl.sgml
View file @
57da4cca
<
!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.7
8 2007/12/02 19:20:32
tgl Exp $ -->
<
!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.7
9 2007/12/03 04:59:55
tgl Exp $ -->
<
chapter
id
=
"ddl"
>
<
chapter
id
=
"ddl"
>
<
title
>
Data
Definition
</
title
>
<
title
>
Data
Definition
</
title
>
...
@@ -2466,8 +2466,9 @@ CREATE TABLE measurement_y2008m01 ( ) INHERITS (measurement);
...
@@ -2466,8 +2466,9 @@ CREATE TABLE measurement_y2008m01 ( ) INHERITS (measurement);
<
listitem
>
<
listitem
>
<
para
>
<
para
>
We
must
add
non
-
overlapping
table
constraints
,
so
that
our
We
must
provide
non
-
overlapping
table
constraints
.
Rather
than
table
creation
script
becomes
:
just
creating
the
partition
tables
as
above
,
the
table
creation
script
should
really
be
:
<
programlisting
>
<
programlisting
>
CREATE
TABLE
measurement_y2006m02
(
CREATE
TABLE
measurement_y2006m02
(
...
@@ -2550,12 +2551,12 @@ CREATE TRIGGER insert_measurement_trigger
...
@@ -2550,12 +2551,12 @@ CREATE TRIGGER insert_measurement_trigger
CREATE
OR
REPLACE
FUNCTION
measurement_insert_trigger
()
CREATE
OR
REPLACE
FUNCTION
measurement_insert_trigger
()
RETURNS
TRIGGER
AS
$$
RETURNS
TRIGGER
AS
$$
BEGIN
BEGIN
IF
(
logdate
&
gt
;=
DATE
'2006-02-01'
AND
logdate
&
lt
;
DATE
'2006-03-01'
)
THEN
IF
(
NEW
.
logdate
&
gt
;=
DATE
'2006-02-01'
AND
NEW
.
logdate
&
lt
;
DATE
'2006-03-01'
)
THEN
INSERT
INTO
measurement_y2006m02
VALUES
(
NEW
.*);
INSERT
INTO
measurement_y2006m02
VALUES
(
NEW
.*);
ELSIF
(
logdate
&
gt
;=
DATE
'2006-03-01'
AND
logdate
&
lt
;
DATE
'2006-04-01'
)
THEN
ELSIF
(
NEW
.
logdate
&
gt
;=
DATE
'2006-03-01'
AND
NEW
.
logdate
&
lt
;
DATE
'2006-04-01'
)
THEN
INSERT
INTO
measurement_y2006m03
VALUES
(
NEW
.*);
INSERT
INTO
measurement_y2006m03
VALUES
(
NEW
.*);
...
...
ELSIF
(
logdate
&
gt
;=
DATE
'2008-01-01'
AND
logdate
&
lt
;
DATE
'2008-02-01'
)
THEN
ELSIF
(
NEW
.
logdate
&
gt
;=
DATE
'2008-01-01'
AND
NEW
.
logdate
&
lt
;
DATE
'2008-02-01'
)
THEN
INSERT
INTO
measurement_y2008m01
VALUES
(
NEW
.*);
INSERT
INTO
measurement_y2008m01
VALUES
(
NEW
.*);
ELSE
ELSE
RAISE
EXCEPTION
'Date out of range. Fix the measurement_insert_trigger() function!'
;
RAISE
EXCEPTION
'Date out of range. Fix the measurement_insert_trigger() function!'
;
...
@@ -2576,6 +2577,15 @@ LANGUAGE plpgsql;
...
@@ -2576,6 +2577,15 @@ LANGUAGE plpgsql;
it
doesn
't need to be updated as often, since branches can be
it
doesn
't need to be updated as often, since branches can be
added in advance of being needed.
added in advance of being needed.
</para>
</para>
<note>
<para>
In practice it might be best to check the newest partition first,
if most inserts go into that partition. For simplicity we have
shown the trigger'
s
tests
in
the
same
order
as
in
other
parts
of
this
example
.
</
para
>
</
note
>
</
listitem
>
</
listitem
>
</
orderedlist
>
</
orderedlist
>
</
para
>
</
para
>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment