head	1.57;
access;
symbols
	REL9_0_0:1.56
	REL9_1_ALPHA1:1.57
	REL9_0_RC1:1.56
	REL9_0_BETA4:1.56
	REL9_0_STABLE:1.56.0.6
	REL9_0_BETA3:1.56
	REL9_0_BETA2:1.56
	REL7_4_29:1.22
	REL8_0_25:1.26
	REL8_1_21:1.28
	REL8_2_17:1.33
	REL8_3_11:1.43
	REL8_4_4:1.52
	REL9_0_BETA1:1.56
	REL9_0_ALPHA5_BRANCH:1.56.0.4
	REL9_0_ALPHA5:1.56
	REL7_4_28:1.22
	REL8_0_24:1.26
	REL8_1_20:1.28
	REL8_2_16:1.33
	REL8_3_10:1.43
	REL8_4_3:1.52
	REL9_0_ALPHA4:1.56
	REL9_0_ALPHA4_BRANCH:1.56.0.2
	REL8_5_ALPHA3:1.54
	REL8_5_ALPHA3_BRANCH:1.54.0.4
	REL7_4_27:1.22
	REL8_0_23:1.26
	REL8_1_19:1.28
	REL8_2_15:1.33
	REL8_3_9:1.43
	REL8_4_2:1.52
	REL8_5_ALPHA2:1.54
	REL8_5_ALPHA2_BRANCH:1.54.0.2
	REL7_4_26:1.22
	REL8_0_22:1.26
	REL8_1_18:1.28
	REL8_2_14:1.33
	REL8_3_8:1.43
	REL8_4_1:1.52
	REL8_5_ALPHA1:1.53
	REL8_5_ALPHA1_BRANCH:1.53.0.2
	REL8_4_STABLE:1.52.0.2
	REL8_4_0:1.52
	REL8_4_RC2:1.52
	REL8_4_RC1:1.52
	REL8_4_BETA2:1.52
	REL8_4_BETA1:1.52
	REL7_4_25:1.22
	REL8_0_21:1.26
	REL8_1_17:1.28
	REL8_2_13:1.33
	REL8_3_7:1.43
	REL7_4_24:1.22
	REL8_0_20:1.26
	REL8_1_16:1.28
	REL8_2_12:1.33
	REL8_3_6:1.43
	REL7_4_23:1.22
	REL8_0_19:1.26
	REL8_1_15:1.28
	REL8_2_11:1.33
	REL8_3_5:1.43
	REL7_4_22:1.22
	REL8_0_18:1.26
	REL8_1_14:1.28
	REL8_2_10:1.33
	REL8_3_4:1.43
	REL7_4_21:1.22
	REL8_0_17:1.26
	REL8_1_13:1.28
	REL8_2_9:1.33
	REL8_3_3:1.43
	REL7_4_20:1.22
	REL8_0_16:1.26
	REL8_1_12:1.28
	REL8_2_8:1.33
	REL8_3_2:1.43
	REL8_2_7:1.33
	REL8_3_1:1.43
	REL8_3_STABLE:1.43.0.2
	REL8_3_0:1.43
	REL8_3_RC2:1.43
	REL7_3_21:1.18.2.1
	REL7_4_19:1.22
	REL8_0_15:1.26
	REL8_1_11:1.28
	REL8_2_6:1.33
	REL8_3_RC1:1.43
	REL8_3_BETA4:1.43
	REL8_3_BETA3:1.42
	REL8_3_BETA2:1.42
	REL8_3_BETA1:1.41
	REL7_3_20:1.18.2.1
	REL7_4_18:1.22
	REL8_0_14:1.26
	REL8_1_10:1.28
	REL8_2_5:1.33
	REL7_3_19:1.18.2.1
	REL7_4_17:1.22
	REL8_0_13:1.26
	REL8_1_9:1.28
	REL8_2_4:1.33
	REL8_0_12:1.26
	REL8_1_8:1.28
	REL8_2_3:1.33
	REL7_3_18:1.18.2.1
	REL7_4_16:1.22
	REL8_0_11:1.26
	REL8_1_7:1.28
	REL8_2_2:1.33
	REL8_0_10:1.26
	REL8_1_6:1.28
	REL8_2_1:1.33
	REL7_4_15:1.22
	REL7_3_17:1.18.2.1
	REL8_2_STABLE:1.33.0.2
	REL8_2_0:1.33
	REL8_2_RC1:1.33
	REL8_2_BETA3:1.33
	REL8_2_BETA2:1.33
	REL8_1_5:1.28
	REL8_0_9:1.26
	REL7_4_14:1.22
	REL7_3_16:1.18.2.1
	REL8_2_BETA1:1.33
	REL7_3_15:1.18.2.1
	REL7_4_13:1.22
	REL8_0_8:1.26
	REL8_1_4:1.28
	REL7_3_14:1.18.2.1
	REL7_4_12:1.22
	REL8_0_7:1.26
	REL8_1_3:1.28
	REL7_3_13:1.18.2.1
	REL7_4_11:1.22
	REL8_0_6:1.26
	REL8_1_2:1.28
	REL7_3_12:1.18.2.1
	REL7_4_10:1.22
	REL8_0_5:1.26
	REL8_1_1:1.28
	REL8_1_STABLE:1.28.0.2
	REL8_1_0:1.28
	REL8_1_0RC1:1.28
	REL8_1_0BETA4:1.28
	REL8_1_0BETA3:1.28
	REL7_3_11:1.18.2.1
	REL7_4_9:1.22
	REL8_0_4:1.26
	REL8_1_0BETA2:1.28
	REL8_1_0BETA1:1.28
	REL7_2_8:1.7
	REL7_3_10:1.18
	REL7_4_8:1.22
	REL8_0_3:1.26
	REL8_0_2:1.26
	REL7_2_7:1.7
	REL7_3_9:1.18
	REL7_4_7:1.22
	REL8_0_1:1.26
	REL8_0_STABLE:1.26.0.4
	REL8_0_0:1.26.0.2
	REL8_0_0RC5:1.26
	REL8_0_0RC4:1.26
	REL8_0_0RC3:1.26
	REL8_0_0RC2:1.26
	REL8_0_0RC1:1.26
	REL8_0_0BETA5:1.26
	REL8_0_0BETA4:1.26
	REL7_4_6:1.22
	REL7_3_8:1.18
	REL7_2_6:1.7
	REL8_0_0BETA3:1.26
	REL8_0_0BETA2:1.26
	REL7_2_5:1.7
	REL7_4_5:1.22
	REL7_3_7:1.18
	REL7_4_4:1.22
	REL8_0_0BETA1:1.26
	REL7_4_3:1.22
	REL7_4_2:1.22
	REL7_3_6:1.18
	REL7_4_1:1.22
	REL7_3_5:1.18
	REL7_4:1.22
	REL7_4_RC2:1.22
	REL7_4_STABLE:1.22.0.2
	REL7_4_RC1:1.22
	REL7_4_BETA5:1.22
	REL7_4_BETA4:1.22
	REL7_4_BETA3:1.22
	REL7_4_BETA2:1.21
	WIN32_DEV:1.20.0.2
	REL7_4_BETA1:1.20
	REL7_3_4:1.18
	REL7_3_2:1.18
	REL7_2_4:1.7
	REL7_3_STABLE:1.18.0.2
	REL7_2_3:1.7
	REL7_2_STABLE:1.7.0.2
	REL7_2:1.7
	REL7_2_RC2:1.7
	REL7_2_RC1:1.7
	REL7_2_BETA5:1.7
	REL7_2_BETA4:1.7
	REL7_2_BETA3:1.7
	REL7_2_BETA2:1.7
	REL7_2_BETA1:1.7
	REL7_1_2:1.3
	REL7_1_STABLE:1.3.0.2
	REL7_1_BETA:1.3
	REL7_1_BETA3:1.3
	REL7_1_BETA2:1.3
	REL7_1:1.3;
locks; strict;
comment	@# @;


1.57
date	2010.08.07.02.44.08;	author tgl;	state Exp;
branches;
next	1.56;

1.56
date	2010.02.12.17.33.21;	author tgl;	state Exp;
branches;
next	1.55;

1.55
date	2010.01.28.23.21.13;	author petere;	state Exp;
branches;
next	1.54;

1.54
date	2009.08.24.03.10.16;	author tgl;	state Exp;
branches;
next	1.53;

1.53
date	2009.07.02.07.03.18;	author petere;	state Exp;
branches;
next	1.52;

1.52
date	2009.01.27.12.40.15;	author petere;	state Exp;
branches;
next	1.51;

1.51
date	2009.01.22.17.27.55;	author petere;	state Exp;
branches;
next	1.50;

1.50
date	2008.12.30.17.11.26;	author tgl;	state Exp;
branches;
next	1.49;

1.49
date	2008.12.28.18.54.01;	author tgl;	state Exp;
branches;
next	1.48;

1.48
date	2008.12.19.16.25.19;	author petere;	state Exp;
branches;
next	1.47;

1.47
date	2008.10.31.09.17.16;	author heikki;	state Exp;
branches;
next	1.46;

1.46
date	2008.10.04.21.56.55;	author tgl;	state Exp;
branches;
next	1.45;

1.45
date	2008.10.03.15.37.18;	author petere;	state Exp;
branches;
next	1.44;

1.44
date	2008.04.10.22.25.26;	author tgl;	state Exp;
branches;
next	1.43;

1.43
date	2007.11.24.20.41.35;	author tgl;	state Exp;
branches;
next	1.42;

1.42
date	2007.10.13.23.06.27;	author tgl;	state Exp;
branches;
next	1.41;

1.41
date	2007.09.11.11.54.42;	author teodor;	state Exp;
branches;
next	1.40;

1.40
date	2007.08.21.01.11.30;	author tgl;	state Exp;
branches;
next	1.39;

1.39
date	2007.04.02.03.49.42;	author tgl;	state Exp;
branches;
next	1.38;

1.38
date	2007.03.13.00.33.44;	author tgl;	state Exp;
branches;
next	1.37;

1.37
date	2007.02.09.03.35.35;	author tgl;	state Exp;
branches;
next	1.36;

1.36
date	2007.01.28.16.16.54;	author neilc;	state Exp;
branches;
next	1.35;

1.35
date	2007.01.20.17.15.43;	author neilc;	state Exp;
branches;
next	1.34;

1.34
date	2006.12.21.16.05.16;	author petere;	state Exp;
branches;
next	1.33;

1.33
date	2006.08.30.23.34.22;	author tgl;	state Exp;
branches;
next	1.32;

1.32
date	2006.08.12.02.52.06;	author tgl;	state Exp;
branches;
next	1.31;

1.31
date	2006.08.04.00.00.13;	author tgl;	state Exp;
branches;
next	1.30;

1.30
date	2006.01.22.05.20.34;	author neilc;	state Exp;
branches;
next	1.29;

1.29
date	2005.11.19.17.39.45;	author adunstan;	state Exp;
branches;
next	1.28;

1.28
date	2005.07.07.20.40.01;	author tgl;	state Exp;
branches;
next	1.27;

1.27
date	2005.06.17.22.32.50;	author tgl;	state Exp;
branches;
next	1.26;

1.26
date	2004.06.18.06.14.25;	author tgl;	state Exp;
branches;
next	1.25;

1.25
date	2004.06.06.21.20.46;	author tgl;	state Exp;
branches;
next	1.24;

1.24
date	2004.01.11.04.58.17;	author neilc;	state Exp;
branches;
next	1.23;

1.23
date	2003.11.29.19.52.14;	author pgsql;	state Exp;
branches;
next	1.22;

1.22
date	2003.09.13.16.44.48;	author momjian;	state Exp;
branches;
next	1.21;

1.21
date	2003.08.26.18.32.23;	author momjian;	state Exp;
branches;
next	1.20;

1.20
date	2003.07.01.19.10.53;	author tgl;	state Exp;
branches
	1.20.2.1;
next	1.19;

1.19
date	2003.03.20.07.02.11;	author momjian;	state Exp;
branches;
next	1.18;

1.18
date	2002.09.02.05.55.43;	author momjian;	state Exp;
branches
	1.18.2.1;
next	1.17;

1.17
date	2002.08.27.04.55.12;	author tgl;	state Exp;
branches;
next	1.16;

1.16
date	2002.08.22.04.51.06;	author momjian;	state Exp;
branches;
next	1.15;

1.15
date	2002.08.11.02.06.32;	author tgl;	state Exp;
branches;
next	1.14;

1.14
date	2002.07.25.10.07.13;	author ishii;	state Exp;
branches;
next	1.13;

1.13
date	2002.07.20.05.16.59;	author momjian;	state Exp;
branches;
next	1.12;

1.12
date	2002.07.20.04.57.13;	author momjian;	state Exp;
branches;
next	1.11;

1.11
date	2002.07.18.04.43.51;	author momjian;	state Exp;
branches;
next	1.10;

1.10
date	2002.06.20.17.09.42;	author momjian;	state Exp;
branches;
next	1.9;

1.9
date	2002.04.05.11.56.55;	author momjian;	state Exp;
branches;
next	1.8;

1.8
date	2002.03.19.02.18.24;	author momjian;	state Exp;
branches;
next	1.7;

1.7
date	2001.09.28.07.59.38;	author thomas;	state Exp;
branches
	1.7.2.1;
next	1.6;

1.6
date	2001.06.12.16.34.27;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	2001.06.12.15.58.34;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	2001.05.27.09.59.30;	author petere;	state Exp;
branches;
next	1.3;

1.3
date	2000.11.22.13.37.44;	author petere;	state Exp;
branches;
next	1.2;

1.2
date	2000.10.01.21.19.09;	author petere;	state Exp;
branches;
next	1.1;

1.1
date	2000.09.29.17.17.37;	author petere;	state Exp;
branches;
next	;

1.7.2.1
date	2005.07.16.19.02.01;	author tgl;	state Exp;
branches;
next	;

1.18.2.1
date	2005.07.16.19.01.50;	author tgl;	state Exp;
branches;
next	;

1.20.2.1
date	2003.09.07.04.37.12;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.57
log
@Recognize functional dependency on primary keys.  This allows a table's
other columns to be referenced without listing them in GROUP BY, so long as
the primary key column(s) are listed in GROUP BY.

Eventually we should also allow functional dependency on a UNIQUE constraint
when the columns are marked NOT NULL, but that has to wait until NOT NULL
constraints are represented in pg_constraint, because we need to have
pg_constraint OIDs for all the conditions needed to ensure functional
dependency.

Peter Eisentraut, reviewed by Alex Hunsaker and Tom Lane
@
text
@# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.56 2010/02/12 17:33:21 tgl Exp $
# This should probably be in an order similar to parallel_schedule.
test: tablespace
test: boolean
test: char
test: name
test: varchar
test: text
test: int2
test: int4
test: int8
test: oid
test: float4
test: float8
test: bit
test: numeric
test: txid
test: uuid
test: enum
test: money
test: strings
test: numerology
test: point
test: lseg
test: box
test: path
test: polygon
test: circle
test: date
test: time
test: timetz
test: timestamp
test: timestamptz
test: interval
test: abstime
test: reltime
test: tinterval
test: inet
test: macaddr
test: tstypes
test: comments
test: geometry
test: horology
test: oidjoins
test: type_sanity
test: opr_sanity
test: insert
test: create_function_1
test: create_type
test: create_table
test: create_function_2
test: create_cast
test: copy
test: copyselect
test: constraints
test: triggers
test: create_misc
test: create_aggregate
test: create_operator
test: create_index
test: drop_if_exists
test: inherit
test: typed_table
test: vacuum
test: create_view
test: sanity_check
test: errors
test: select
test: select_into
test: select_distinct
test: select_distinct_on
test: select_implicit
test: select_having
test: subselect
test: union
test: case
test: join
test: aggregates
test: transactions
ignore: random
test: random
test: portals
test: arrays
test: btree_index
test: hash_index
test: update
test: delete
test: namespace
test: prepared_xacts
test: privileges
test: misc
test: rules
test: select_views
test: portals_p2
test: foreign_key
test: cluster
test: dependency
test: guc
test: bitmapops
test: combocid
test: tsearch
test: tsdicts
test: foreign_data
test: window
test: xmlmap
test: functional_deps
test: plancache
test: limit
test: plpgsql
test: copy2
test: temp
test: domain
test: rangefuncs
test: prepare
test: without_oid
test: conversion
test: truncate
test: alter_table
test: sequence
test: polymorphism
test: rowtypes
test: returning
test: largeobject
test: with
test: xml
test: stats
@


1.56
log
@Extend the set of frame options supported for window functions.

This patch allows the frame to start from CURRENT ROW (in either RANGE or
ROWS mode), and it also adds support for ROWS n PRECEDING and ROWS n FOLLOWING
start and end points.  (RANGE value PRECEDING/FOLLOWING isn't there yet ---
the grammar works, but that's all.)

Hitoshi Harada, reviewed by Pavel Stehule
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.55 2010/01/28 23:21:13 petere Exp $
d106 1
@


1.55
log
@Type table feature

This adds the CREATE TABLE name OF type command, per SQL standard.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.54 2009/08/24 03:10:16 tgl Exp $
d92 1
a94 1
test: rules
@


1.54
log
@Run the "tablespace" regression test first not last.  The former placement
renders useless one of the few test methodologies we have for WAL replay,
which is to intentionally crash the system just after completing the
regression tests and see if it recovers to the expected database state.
The reason is that DROP TABLESPACE forces a checkpoint, so there's essentially
no WAL available for replay after the tests complete.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.53 2009/07/02 07:03:18 petere Exp $
d63 1
@


1.53
log
@Regression test for XML mapping functionality

I wrote this one while chasing down some bugs in the closing days of 8.4.  It
could be useful in the long run.  This area of the code had no test coverage
at all before.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.52 2009/01/27 12:40:15 petere Exp $
d3 1
a124 1
test: tablespace
@


1.52
log
@Revert updatable views
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.51 2009/01/22 17:27:55 petere Exp $
d103 1
@


1.51
log
@Automatic view update rules

Bernd Helmle
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.50 2008/12/30 17:11:26 tgl Exp $
a102 1
test: view_update
@


1.50
log
@Reduce the last group of parallel regression tests to 19 tests, per failure
on buildfarm member bear.  Sync the test order in serial_schedule with that
in parallel_schedule.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.49 2008/12/28 18:54:01 tgl Exp $
d103 1
@


1.49
log
@Support window functions a la SQL:2008.

Hitoshi Harada, with some kibitzing from Heikki and Tom.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.48 2008/12/19 16:25:19 petere Exp $
d100 3
a112 2
test: tsdicts
test: foreign_data
a119 1
test: window
@


1.48
log
@SQL/MED catalog manipulation facilities

This doesn't do any remote or external things yet, but it gives modules
like plproxy and dblink a standardized and future-proof system for
managing their connection information.

Martin Pihlak and Peter Eisentraut
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.47 2008/10/31 09:17:16 heikki Exp $
d119 1
@


1.47
log
@Add test case for CREATE CAST.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.46 2008/10/04 21:56:55 tgl Exp $
d111 1
@


1.46
log
@Implement SQL-standard WITH clauses, including WITH RECURSIVE.

There are some unimplemented aspects: recursive queries must use UNION ALL
(should allow UNION too), and we don't have SEARCH or CYCLE clauses.
These might or might not get done for 8.4, but even without them it's a
pretty useful feature.

There are also a couple of small loose ends and definitional quibbles,
which I'll send a memo about to pgsql-hackers shortly.  But let's land
the patch now so we can get on with other development.

Yoshiyuki Asaba, with lots of help from Tatsuo Ishii and Tom Lane
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.45 2008/10/03 15:37:18 petere Exp $
d51 1
@


1.45
log
@Add regression test for macaddr type.  Enhance documentation about accepted
input formats.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.44 2008/04/10 22:25:26 tgl Exp $
d117 1
@


1.44
log
@Replace "amgetmulti" AM functions with "amgetbitmap", in which the whole
indexscan always occurs in one call, and the results are returned in a
TIDBitmap instead of a limited-size array of TIDs.  This should improve
speed a little by reducing AM entry/exit overhead, and it is necessary
infrastructure if we are ever to support bitmap indexes.

In an only slightly related change, add support for TIDBitmaps to preserve
(somewhat lossily) the knowledge that particular TIDs reported by an index
need to have their quals rechecked when the heap is visited.  This facility
is not really used yet; we'll need to extend the forced-recheck feature to
plain indexscans before it's useful, and that hasn't been coded yet.
The intent is to use it to clean up 8.3's horrid @@@@@@ kluge for text search
with weighted queries.  There might be other uses in future, but that one
alone is sufficient reason.

Heikki Linnakangas, with some adjustments by me.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.43 2007/11/24 20:41:35 tgl Exp $
d38 1
@


1.43
log
@Add missed entry for new money regression test.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.42 2007/10/13 23:06:27 tgl Exp $
d95 1
@


1.42
log
@Migrate the former contrib/txid module into core.  This will make it easier
for Slony and Skytools to depend on it.  Per discussion.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.41 2007/09/11 11:54:42 teodor Exp $
d19 1
@


1.41
log
@Add regression tests for ispell, synonym and thesaurus dictionaries.
Rename synonym.syn.sample and thesaurs.ths.sample to
synonym_sample.syn and thesaurs_sample.ths accordingly to be able to use they
in regression test.

Ispell dictionary uses synthetic simple dictionary files.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.40 2007/08/21 01:11:30 tgl Exp $
d16 1
@


1.40
log
@Tsearch2 functionality migrates to core.  The bulk of this work is by
Oleg Bartunov and Teodor Sigaev, but I did a lot of editorializing,
so anything that's broken is probably my fault.

Documentation is nonexistent as yet, but let's land the patch so we can
get some portability testing done.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.39 2007/04/02 03:49:42 tgl Exp $
d105 1
@


1.39
log
@Support enum data types.  Along the way, use macros for the values of
pg_type.typtype whereever practical.  Tom Dunstan, with some kibitzing
from Tom Lane.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.38 2007/03/13 00:33:44 tgl Exp $
d36 1
d38 2
a42 2
test: geometry
test: horology
d94 1
@


1.38
log
@First phase of plan-invalidation project: create a plan cache management
module and teach PREPARE and protocol-level prepared statements to use it.
In service of this, rearrange utility-statement processing so that parse
analysis does not assume table schemas can't change before execution for
utility statements (necessary because we don't attempt to re-acquire locks
for utility statements when reusing a stored plan).  This requires some
refactoring of the ProcessUtility API, but it ends up cleaner anyway,
for instance we can get rid of the QueryContext global.

Still to do: fix up SPI and related code to use the plan cache; I'm tempted to
try to make SQL functions use it too.  Also, there are at least some aspects
of system state that we want to ensure remain the same during a replan as in
the original processing; search_path certainly ought to behave that way for
instance, and perhaps there are others.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.37 2007/02/09 03:35:35 tgl Exp $
d17 1
@


1.37
log
@Combine cmin and cmax fields of HeapTupleHeaders into a single field, by
keeping private state in each backend that has inserted and deleted the same
tuple during its current top-level transaction.  This is sufficient since
there is no need to be able to determine the cmin/cmax from any other
transaction.  This gets us back down to 23-byte headers, removing a penalty
paid in 8.0 to support subtransactions.  Patch by Heikki Linnakangas, with
minor revisions by moi, following a design hashed out awhile back on the
pghackers list.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.36 2007/01/28 16:16:54 neilc Exp $
d92 1
@


1.36
log
@Add a new builtin type, "uuid". This implements a UUID type, similar to
that defined in RFC 4122. This patch includes the basic implementation,
plus regression tests. Documentation and perhaps some additional
functionality will come later. Catversion bumped.

Patch from Gevik Babakhani; review from Peter, Tom, and myself.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.35 2007/01/20 17:15:43 neilc Exp $
d91 1
@


1.35
log
@Regression tests for large objects. Patch from Jeremy Drake.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.34 2006/12/21 16:05:16 petere Exp $
d16 1
@


1.34
log
@Initial SQL/XML support: xml data type and initial set of functions.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.33 2006/08/30 23:34:22 tgl Exp $
d105 1
@


1.33
log
@Extend COPY to support COPY (SELECT ...) TO ...

Bernd Helmle
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.32 2006/08/12 02:52:06 tgl Exp $
d105 1
@


1.32
log
@Add INSERT/UPDATE/DELETE RETURNING, with basic docs and regression tests.
plpgsql support to come later.  Along the way, convert execMain's
SELECT INTO support into a DestReceiver, in order to eliminate some ugly
special cases.

Jonah Harris and Tom Lane
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.31 2006/08/04 00:00:13 tgl Exp $
d46 1
@


1.31
log
@Add some basic tests of GUC behavior.
Joachim Wieland
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.30 2006/01/22 05:20:34 neilc Exp $
d103 1
@


1.30
log
@Allow an optional alias for the target table to be specified for UPDATE
and DELETE. If specified, the alias must be used instead of the full
table name. Also, the alias currently cannot be used in the SET clause
of UPDATE.

Patch from Atsushi Ogawa, various editorialization by Neil Conway.
Along the way, make the rowtypes regression test pass if add_missing_from
is enabled, and add a new (skeletal) regression test for DELETE.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.29 2005/11/19 17:39:45 adunstan Exp $
d87 2
a104 1
test: dependency
@


1.29
log
@
DROP objecttype IF EXISTS for the following objects:
  table view index sequence schema type domain conversion
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.28 2005/07/07 20:40:01 tgl Exp $
d77 1
@


1.28
log
@Track dependencies on shared objects (which is to say, roles; we already
have adequate mechanisms for tracking the contents of databases and
tablespaces).  This solves the longstanding problem that you can drop a
user who still owns objects and/or has access permissions.
Alvaro Herrera, with some kibitzing from Tom Lane.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.27 2005/06/17 22:32:50 tgl Exp $
d52 1
@


1.27
log
@Two-phase commit.  Original patch by Heikki Linnakangas, with additional
hacking by Alvaro Herrera and Tom Lane.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql/src/test/regress/serial_schedule,v 1.26 2004/06/18 06:14:25 tgl Exp $
d101 1
@


1.26
log
@Tablespaces.  Alternate database locations are dead, long live tablespaces.

There are various things left to do: contrib dbsize and oid2name modules
need work, and so does the documentation.  Also someone should think about
COMMENT ON TABLESPACE and maybe RENAME TABLESPACE.  Also initlocation is
dead, it just doesn't know it yet.

Gavin Sherry and Tom Lane.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql-server/src/test/regress/serial_schedule,v 1.25 2004/06/06 21:20:46 tgl Exp $
d77 1
@


1.25
log
@Add some regression tests for composite-type operations.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql-server/src/test/regress/serial_schedule,v 1.24 2004/01/11 04:58:17 neilc Exp $
d99 1
@


1.24
log
@Add CREATE TRIGGER, CREATE INDEX, and CREATE SEQUENCE to the list of
expressions supported by CREATE SCHEMA.

Also added the beginning of some regression tests for CREATE SCHEMA;
plenty more work is needed here.
@
text
@d1 1
a1 1
# $PostgreSQL: pgsql-server/src/test/regress/serial_schedule,v 1.23 2003/11/29 19:52:14 pgsql Exp $
d97 1
@


1.23
log
@
$Header: -> $PostgreSQL Changes ...
@
text
@d1 1
a1 1
# $PostgreSQL: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.22 2003/09/13 16:44:48 momjian Exp $
d76 1
@


1.22
log
@With pg_autovacuum becoming increasingly popular it's important to
have a working stats collector.  This test is able to discover the
problem that was present in 7.4 Beta 2.

Manfred Koizar
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.21 2003/08/26 18:32:23 momjian Exp $
@


1.21
log
@This patch adds a new regression test for the UPDATE command. Right
now all that is tested is Rod Taylor's recent addition to allow
this syntax:

    UPDATE ... SET <col> = DEFAULT;

If anyone else would like to add more UPDATE tests, go ahead --
I just wanted to write a test for the above functionality, and
couldn't see an existing test that it would be appropriate
to add to.

Neil Conway
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.20 2003/07/01 19:10:53 tgl Exp $
d96 1
@


1.20
log
@Aggregates can be polymorphic, using polymorphic implementation functions.
It also works to create a non-polymorphic aggregate from polymorphic
functions, should you want to do that.  Regression test added, docs still
lacking.  By Joe Conway, with some kibitzing from Tom Lane.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.19 2003/03/20 07:02:11 momjian Exp $
d75 1
@


1.20.2.1
log
@Update this branch to match CVS head, includes WIN32 improvements.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.21 2003/08/26 18:32:23 momjian Exp $
a74 1
test: update
@


1.19
log
@Todo items:
Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values

Also updated create sequence docs to mention NO MINVALUE, & NO MAXVALUE.

New Files:
doc/src/sgml/ref/alter_sequence.sgml
src/test/regress/expected/sequence.out
src/test/regress/sql/sequence.sql


ALTER SEQUENCE is NOT transactional.  It behaves similarly to setval().
It matches the proposed SQL200N spec, as well as Oracle in most ways --
Oracle lacks RESTART WITH for some strange reason.

--
Rod Taylor <rbt@@rbt.ca>
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.18 2002/09/02 05:55:43 momjian Exp $
d94 1
@


1.18
log
@Okay, attached is a patch that moves the alter table regression test
into a separate parallel group. I can't confirm that this fixes the
problem for me (since it only occurs about one in ten or one in twenty
runs), but I think it's a good bet that it does...

Neil Conway
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.17 2002/08/27 04:55:12 tgl Exp $
d93 1
@


1.18.2.1
log
@Mark the geometry regression test as an ignorable failure in the pre-7.4
branches.  Per discussion, this seems saner than trying to maintain
last-significant-digit regression test outputs for all supported platforms.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.18 2002/09/02 05:55:43 momjian Exp $
a37 1
ignore: geometry
@


1.17
log
@PREPARE/EXECUTE statements.  Patch by Neil Conway, some kibitzing
from Tom Lane.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.16 2002/08/22 04:51:06 momjian Exp $
a77 1
test: alter_table
d92 1
@


1.16
log
@# Disallow TRUNCATE on tables that are involved in referential
constraints


The issue with finding and removing foreign key constraints is no longer
an issue, so please apply the attached.

It does NOT check for rules or on delete triggers (old style foreign
keys) as those are difficult to deal with (remove, truncate, re-add).

Rod Taylor
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.15 2002/08/11 02:06:32 tgl Exp $
d89 1
@


1.15
log
@Make cluster regress test functional.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql-server/src/test/regress/serial_schedule,v 1.14 2002/07/25 10:07:13 ishii Exp $
d91 1
@


1.14
log
@Implement DROP CONVERSION
Add regression test
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.13 2002/07/20 05:16:59 momjian Exp $
d82 1
@


1.13
log
@oid is needed, it is added at the end of the struct (after the null
bitmap, if present).

Per Tom Lane's suggestion the information whether a tuple has an oid
or not is carried in the tuple descriptor.  For debugging reasons
tdhasoid is of type char, not bool.  There are predefined values for
WITHOID, WITHOUTOID and UNDEFOID.

This patch has been generated against a cvs snapshot from last week
and I don't expect it to apply cleanly to current sources.  While I
post it here for public review, I'm working on a new version against a
current snapshot.  (There's been heavy activity recently; hope to
catch up some day ...)

This is a long patch;  if it is too hard to swallow, I can provide it
in smaller pieces:

Part 1:  Accessor macros
Part 2:  tdhasoid in TupDesc
Part 3:  Regression test
Part 4:  Parameter withoid to heap_addheader
Part 5:  Eliminate t_oid from HeapTupleHeader

Part 2 is the most hairy part because of changes in the executor and
even in the parser;  the other parts are straightforward.

Up to part 4 the patched postmaster stays binary compatible to
databases created with an unpatched version.  Part 5 is small (100
lines) and finally breaks compatibility.

Manfred Koizar
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.12 2002/07/20 04:57:13 momjian Exp $
d89 1
@


1.12
log
@This patch fixes a regression caused by my recent changes to heap
tuple header.  The fix is based on the thought that HEAP_MOVED_IN is
not needed any more as soon as HEAP_XMIN_COMMITTED has been set.  So
in tqual.c and vacuum.c the HEAP_MOVED bits are cleared when
HEAP_XMIN_COMMITTED is set.

Vacuum robustness is enhanced by rearranging ifs, so that we have a
chance to elog(ERROR, ...) before an assertion fails.

A new regression test is included.

Manfred Koizar
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.11 2002/07/18 04:43:51 momjian Exp $
d88 1
@


1.11
log
@The attached patch (against HEAD) implements

  COPY x (a,d,c,b) from stdin;
  COPY x (a,c) to stdout;

as well as the corresponding changes to pg_dump to use the new
functionality.  This functionality is not available when using
the BINARY option.  If a column is not specified in the COPY FROM
statement, its default values will be used.

In addition to this functionality, I tweaked a couple of the
error messages emitted by the new COPY <options> checks.

Brent Verner
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.10 2002/06/20 17:09:42 momjian Exp $
d53 1
@


1.10
log
@Attached is a regression test patch for SRFs. I based it on the test
scripts that I have been using, minus the C function tests and without
calls to random() -- figured random() wouldn't work too well for a
regression test ;-)

Joe Conway
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.9 2002/04/05 11:56:55 momjian Exp $
d83 1
@


1.9
log
@Add INSERT(..., DEFAULT, ).

Rod Taylor
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.8 2002/03/19 02:18:24 momjian Exp $
d85 1
a85 1

@


1.8
log
@Add DOMAIN support.  Includes manual pages and regression tests, from
Rod Taylor.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.7 2001/09/28 07:59:38 thomas Exp $
d40 1
@


1.7
log
@Add separate regression tests for timetz and the new timestamptz type.
Modify the timestamp test to reflect the "no time zone" behavior of this
 new code; timestamptz resembles the old timestamp code.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.6 2001/06/12 16:34:27 momjian Exp $
d83 2
@


1.7.2.1
log
@Mark the geometry regression test as an ignorable failure in the pre-7.4
branches.  Per discussion, this seems saner than trying to maintain
last-significant-digit regression test outputs for all supported platforms.
@
text
@d1 1
a1 1
# $Header: /cvsroot/pgsql/src/test/regress/serial_schedule,v 1.7 2001/09/28 07:59:38 thomas Exp $
a37 1
ignore: geometry
@


1.6
log
@Back out has_table_privilege patch.
@
text
@d1 1
a1 1
# $Header: /home/projects/pgsql/cvsroot/pgsql/src/test/regress/serial_schedule,v 1.5 2001/06/12 15:58:34 momjian Exp $
d26 1
d28 1
@


1.5
log
@OK -- here's take #5.

It "make"s and "make check"s clean against current cvs tip.

There are now both Text and Name variants, and the regression test support
is rolled into the patch. Note that to be complete wrt Name based variants,
there are now 12 user visible versions of has_table_privilege:

has_table_privilege(Text usename, Text relname, Text priv_type)
has_table_privilege(Text usename, Name relname, Text priv_type)
has_table_privilege(Name usename, Text relname, Text priv_type)
has_table_privilege(Name usename, Name relname, Text priv_type)
has_table_privilege(Text relname, Text priv_type) /* assumes current_user */
has_table_privilege(Name relname, Text priv_type) /* assumes current_user */
has_table_privilege(Text usename, Oid reloid, Text priv_type)
has_table_privilege(Name usename, Oid reloid, Text priv_type)
has_table_privilege(Oid reloid, Text priv_type)  /* assumes current_user */
has_table_privilege(Oid usesysid, Text relname, Text priv_type)
has_table_privilege(Oid usesysid, Name relname, Text priv_type)
has_table_privilege(Oid usesysid, Oid reloid, Text priv_type)

For the Text based inputs, a new internal function, get_Name is used
(shamelessly copied from get_seq_name in sequence.c) to downcase if not
quoted, or remove quotes if quoted, and truncate. I also added a few test
cases for the downcasing, quote removal, and Name based variants to the
regression test.

Joe Conway
@
text
@d1 1
a1 1
# $Header: /home/projects/pgsql/cvsroot/pgsql/src/test/regress/serial_schedule,v 1.4 2001/05/27 09:59:30 petere Exp $
a71 1
test: has_table_priv
@


1.4
log
@Make UPDATE and DELETE privileges distinct.  Add REFERENCES and TRIGGER
privileges.  INSERT and COPY FROM now require INSERT (only).  Add
privileges regression test.
@
text
@d1 1
a1 1
# $Header: /home/projects/pgsql/cvsroot/pgsql/src/test/regress/serial_schedule,v 1.3 2000/11/22 13:37:44 petere Exp $
d72 1
@


1.3
log
@Bit string regression test
from Adriaan Joubert <a.joubert@@albourne.com>
@
text
@d1 1
a1 1
# $Header: /home/projects/pgsql/cvsroot/pgsql/src/test/regress/serial_schedule,v 1.2 2000/10/01 21:19:09 petere Exp $
d71 1
@


1.2
log
@Fix test order
@
text
@d1 1
a1 1
# $Header$
d14 1
@


1.1
log
@New unified regression test driver, test/regress makefile cleanup,
add "check" and "installcheck" targets, straighten out make variable naming
of host_os, host_cpu, etc.
@
text
@d1 2
a7 1
test: strings
d14 2
a22 1
test: geometry
a29 1
test: horology
d35 2
d41 1
a43 1
test: copy
d47 2
a49 1
test: create_index
a66 1
test: misc
d70 1
d75 1
a78 1
test: numeric
@
