In the previous generation of analyze, gpdb provided features to merge
statistics such as MCVs (Most common values) and histograms for the root
or midlevel partitions from the leaf partition's statistics.

This commit imports the utility functions for merging MCVs and
histograms and modifies based on the needs of current version.
Signed-off-by: NBhunvesh Chaudhary <bchaudhary@pivotal.io>

Remove the concept of filespaces, revert tablespaces to work the same as
in upstream.

There is some leftovers in management tools. I don't know how to test all
that, and I was afraid of touching things I can't run. Also, we may need
to create replacements for some of those things on top of tablespaces, to
make the management of tablespaces easier, and it might be easier to modify
the existing tools than write them from scratch. (Yeah, you could always
look at the git history, but still.)

Per the discussion on gpdb-dev mailing list, the plan is to cherry-pick
commit 16d8e594 from PostgreSQL 9.2, to make it possible to have a
different path for a tablespace in the primary and its mirror. But that's
not included in this commit yet.

TODO: Make temp_tablespaces work.
TODO: Make pg_dump do something sensible, when dumping from a GPDB 5 cluster
that uses filespaces. Same with pg_upgrade.

Discussion: https://groups.google.com/a/greenplum.org/d/msg/gpdb-dev/sON4lraPEqg/v3lkM587BAAJ

Signed-off-by: NAdam Lee <ali@pivotal.io>

utils/resgroup/resgroup.c.

Signed-off-by Richard Guo <riguo@pivotal.io>
Signed-off-by Gang Xiong <gxiong@pivotal.io>

There are two default resource groups 'default_group' and 'admin_group',
to create more please use the CREATE RESOURCE GROUP command, group
options can be specified with the WITH clause, at the moment
'cpu_rate_limit' and 'memory_limit' are mandatory, other options are
all optional.

    -- create a resource group
    CREATE RESOURCE GROUP rg1 WITH (
        concurrency=1,
        cpu_rate_limit=.2,
        memory_limit=.2
    );
    -- query the resource group
    SELECT oid FROM pg_resgroup WHERE rsgname='rg1';
    SELECT * from gp_toolkit.gp_resgroup_config
        WHERE groupname='rg1';
    -- create/alter a role and assign it to this group
    CREATE ROLE r1 RESOURCE GROUP rg1;
    ALTER ROLE r2 RESOURCE GROUP rg1;

*NOTE*: this commit only implement the SQL syntax, the actual resource
limitation will not take effect at the moment as the resource group is
still under development.

*NOTE*: test cases are not included in this commit as once a testing
resgroup is created it can't be dropped due to lack of DROP syntax, so
the test case can't be re-run and will introduce side-effect to the
system. So it's better to provide test cases after the DROP RESOURCE
GROUP is implemented.
Signed-off-by: NNing Yu <nyu@pivotal.io>

- continue to merge the remaining part of extension framework,
include alter extension, extension view, extension upgrade,
psql support.
- Make plpgsql available as an extension.
- Support dump for extension.
- Use new oid dispatch method to for extension oid

commit d9572c4e
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Tue Feb 8 16:08:41 2011 -0500

    Core support for "extensions", which are packages of SQL objects.

    This patch adds the server infrastructure to support extensions.
    There is still one significant loose end, namely how to make it play nice
    with pg_upgrade, so I am not yet committing the changes that would make
    all the contrib modules depend on this feature.

    In passing, fix a disturbingly large amount of breakage in
    AlterObjectNamespace() and callers.

    Dimitri Fontaine, reviewed by Anssi Kääriäinen,
    Itagaki Takahiro, Tom Lane, and numerous others

commit 5bc178b8
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Wed Feb 9 11:55:32 2011 -0500

    Implement "ALTER EXTENSION ADD object".

    This is an essential component of making the extension feature usable;
    first because it's needed in the process of converting an existing
    installation containing "loose" objects of an old contrib module into
    the extension-based world, and second because we'll have to use it
    in pg_dump --binary-upgrade, as per recent discussion.

    Loosely based on part of Dimitri Fontaine's ALTER EXTENSION UPGRADE
    patch.

commit 01467d3e
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Thu Feb 10 17:36:44 2011 -0500

    Extend "ALTER EXTENSION ADD object" to permit "DROP object" as well.

    Per discussion, this is something we should have sooner rather than later,
    and it doesn't take much additional code to support it.

commit 12147499
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date:   Fri Feb 11 21:25:20 2011 -0500

    Add support for multiple versions of an extension and ALTER EXTENSION UPDATE.

    This follows recent discussions, so it's quite a bit different from
    Dimitri's original.  There will probably be more changes once we get a bit
    of experience with it, but let's get it in and start playing with it.

    This is still just core code.  I'll start converting contrib modules
    shortly.

    Dimitri Fontaine and Tom Lane

tablecmds.c is huge, and it's inherited from upstream. This makes diffing
and merging with upstream a little bit easier.

This replaces most of the Greenplum code used to ANALYZE a relation with
the upstream implementation.

I did not adopt the upstream block-sampling method of collecting the
sample, however. That would difficult to make work with GPDB, because the
upstream code won't work as is with Append-only tables, and we would also
need to somehow dispatch the block-sampling to all the segments. So the
simplistic "SELECT ... WHERE random() < threshold" method is still used to
collect the sample. However, it's now just a straightforward read-only
query, we no longer create a table to hold the sample, which makes it a lot
cheaper for small tables.

This should make merging with upstream easier. This should also speed up
ANALYZE considerably, as we now collect the sample of rows in one query,
and calculate the stats for each column in-memory, instead of issuing
separate queries for each column.

It was just syntax and catalogs, you couldn't actually do anything useful
with it. Remove it, so that we have less code to maintain, until it's time
to merge this stuff from upstream again when we merge with PostgreSQL 8.4.
It's probably easier to merge this back at that point than maintain this
backported version in the meanwhile. Less effort now, until we reach that
point, and once we get to the point in 8.4 that we merge this in, we'll
have all the preceding patches applied already, so it should merge quite
smoothly.

- collowner field
- CREATE COLLATION
- ALTER COLLATION
- DROP COLLATION
- COMMENT ON COLLATION
- integration with extensions
- pg_dump support for the above
- dependency management
- psql tab completion
- psql \dO command

This patch adds the server infrastructure to support extensions.
There is still one significant loose end, namely how to make it play nice
with pg_upgrade, so I am not yet committing the changes that would make
all the contrib modules depend on this feature.

In passing, fix a disturbingly large amount of breakage in
AlterObjectNamespace() and callers.

Dimitri Fontaine, reviewed by Anssi Kääriäinen,
Itagaki Takahiro, Tom Lane, and numerous others

This is intended as infrastructure to support integration with label-based
mandatory access control systems such as SE-Linux. Further changes (mostly
hooks) will be needed, but this is a big chunk of it.

KaiGai Kohei and Robert Haas

The current implementation fires an AFTER ROW trigger for each tuple that
looks like it might be non-unique according to the index contents at the
time of insertion.  This works well as long as there aren't many conflicts,
but won't scale to massive unique-key reassignments.  Improving that case
is a TODO item.

Dean Rasheed

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

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.

RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL,
DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid
confusion with the pre-existing RESET variants: the DISCARD
commands are not actually similar to RESET. Patch from Marko
Kreen, with some minor editorialization.

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.

$Header: -> $PostgreSQL Changes ...

from Tom Lane.

documentation (xindex.sgml should be rewritten), need to teach pg_dump
about it, need to update contrib modules that currently build pg_opclass
entries by hand.  Original patch by Bill Studenmund, grammar adjustments
and general update for 7.3 by Tom Lane.

This is the first cut toward CREATE CONVERSION/DROP CONVERSION implementaion.
The commands can now add/remove tuples to the new pg_conversion system
catalog, but that's all. Still need work to make them actually working.
Documentations, regression tests also need work.

have been divided according to the type of object manipulated - so ALTER
TABLE code is in tablecmds.c, aggregate commands in aggregatecmds.c and
so on.

A few common support routines remain in define.c (prototypes in
src/include/commands/defrem.h).

No code has been changed except for includes to reflect the new files.
The prototypes for aggregatecmds.c, functioncmds.c, operatorcmds.c,
and typecmds.c remain in src/include/commands/defrem.h.

From John Gray <jgray@azuli.co.uk>

because index locking issues are not handled correctly yet.  Need to go
work on the index AMs next.

to one another. Sort out builddir vs srcdir variable namings. Remove some
now obsoleted make variables.

the src/include tree, so that -I backend is no longer necessary anywhere.
Also, clean up some bit rot in contrib tree.

The following patch extends the COMMENT ON functionality to the
rest of the database objects beyond just tables, columns, and views. The
grammer of the COMMENT ON statement now looks like:

COMMENT ON [
  [ DATABASE | INDEX | RULE | SEQUENCE | TABLE | TYPE | VIEW ] <objname>
|

  COLUMN <relation>.<attribute> |
  AGGREGATE <aggname> <aggtype> |
  FUNCTION <funcname> (arg1, arg2, ...) |
  OPERATOR <op> (leftoperand_typ rightoperand_typ) |
  TRIGGER <triggername> ON relname>

Mike Mascari
(mascarim@yahoo.com)

it seems.

Move files to deadcode.