- 31 12月, 2015 1 次提交
-
-
由 Heikki Linnakangas 提交于
Use the standard initdb mechanism for it, instead of having bespoken code in gpinitsystem. Also remove the unnecessarily complicated logic to generate gp_toolkit.sql from gp_toolkit.sql.in. All the JETPACK_* variables were constants, and there is particular need in making the gp_toolkit functions relocatable to different schemas or prefixes, so just hardcode them and remove the sed magic. Rewrite the file header of gp_toolkit.sql. The legal blurp is not needed, make the header look more like that of information_schema.sql and system_views.sql. Remove compaction_info.sql. It was only needed for old in-place upgrade from 4.3.x to 4.3.4.2, which is not relevant for master branch. Fix the "jetpack" bugbuster regression test. It was originally written to test the gp_toolkit views, but gp_toolkit was in fact not installed in bugbuster, and the expected output just contained a bunch of "relation does not exist" errors. Now it actually tests gp_toolkit again. Some of the test queries didn't produce repeateable results, due to differing oids, differences in table sizes, and other tables created by previous tests, so fixed those too. This has a small user-visible difference: gp_toolkit schema is now also installed in template0. That caused the difference in the expected outputs: pg_regress creates the "regression" database using template0 as the template, so gp_toolkit used to not be installed in it, but it is now.
-
- 18 11月, 2015 1 次提交
-
-
由 Heikki Linnakangas 提交于
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.
-
- 12 11月, 2015 1 次提交
-
-
由 Heikki Linnakangas 提交于
This splits pg_proc.h into two parts: pg_proc.h and pg_proc_gp.h. After the split, pg_proc.h contains functions we've inherited from upstream, and is mostly identical to the upstream version. This makes diffing and merging with upstream easier. All the upstream functions have been removed from pg_proc.sql, as they are no longer auto-generated. Instead of modifying pg_proc.h, catullus.pl is now used to create pg_proc_gp.h, which contains all the auto-generated DATA entries for the functions in pg_proc.sql. For the upstream-inherited DATA entries in pg_proc.h, remove the columns that are not present in upstream. This was needed again to make pg_proc.h closer to the upstream version. Also, remove auto-generated comments and revert whitespace changes compared to upstream. To compensate for the missing columns, introduce a new perl script, processs_col_defaults.pl that is run at build time, which adds the missing columns back to any DATA rows that miss them, before they are fed to genbki.sh. All the GPDB-added columns are annotated with a magic GPDB_COLUMN_DEFAULT() macro, similar to the CATALOG() and DATA() macros which tells process_col_defaults.pl what values to insert into the missing columns. Remove tidycat2 regression test. It tested that all the functions in pg_catalog came from pg_proc.sql, but that is no longer true. Only the GPDB-added ones are now in pg_proc.sql.
-
- 28 10月, 2015 1 次提交
-
-
- 23 12月, 2006 1 次提交
-
-
由 Tom Lane 提交于
cases. Operator classes now exist within "operator families". While most families are equivalent to a single class, related classes can be grouped into one family to represent the fact that they are semantically compatible. Cross-type operators are now naturally adjunct parts of a family, without having to wedge them into a particular opclass as we had done originally. This commit restructures the catalogs and cleans up enough of the fallout so that everything still works at least as well as before, but most of the work needed to actually improve the planner's behavior will come later. Also, there are not yet CREATE/DROP/ALTER OPERATOR FAMILY commands; the only way to create a new family right now is to allow CREATE OPERATOR CLASS to make one by default. I owe some more documentation work, too. But that can all be done in smaller pieces once this infrastructure is in place.
-
- 31 7月, 2006 1 次提交
-
-
由 Tom Lane 提交于
created in the bootstrap phase proper, rather than added after-the-fact by initdb. This is cleaner than before because it allows us to retire the undocumented ALTER TABLE ... CREATE TOAST TABLE command, but the real reason I'm doing it is so that toast tables of shared catalogs will now have predetermined OIDs. This will allow a reasonably clean solution to the problem of locking tables before we load their relcache entries, to appear in a forthcoming patch.
-
- 12 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
comments on cluster global objects like databases, tablespaces, and roles. It touches a lot of places, but not much in the way of big changes. The only design decision I made was to duplicate the query and manipulation functions rather than to try and have them handle both shared and local comments. I believe this is simpler for the code and not an issue for callers because they know what type of object they are dealing with. This has resulted in a shobj_description function analagous to obj_description and backend functions [Create/Delete]SharedComments mirroring the existing [Create/Delete]Comments functions. pg_shdescription.h goes into src/include/catalog/ Kris Jurka
-
- 10 12月, 2005 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 09 9月, 2005 1 次提交
-
-
由 Tom Lane 提交于
for procedural languages. This replaces the hard-wired table I had originally proposed as a stopgap solution. For the moment, the initial contents only include languages shipped with the core distribution.
-
- 14 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
few loose ends to be dealt with, but it seems to work. Alvaro Herrera, based on the contrib code by Matthew O'Connor.
-
- 08 7月, 2005 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 28 6月, 2005 1 次提交
-
-
由 Tom Lane 提交于
and pg_auth_members. There are still many loose ends to finish in this patch (no documentation, no regression tests, no pg_dump support for instance). But I'm going to commit it now anyway so that Alvaro can make some progress on shared dependencies. The catalog changes should be pretty much done.
-
- 22 7月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
(fairly closely, I hope) to the current PL/Perl implementation. David Fetter
-
- 18 6月, 2004 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 04 1月, 2004 1 次提交
-
-
由 Tom Lane 提交于
run the data through cpp, and we know of at least one platform where unusual cpp behavior breaks the process. So remove the cpp step, and make consequent simplifications.
-
- 30 11月, 2003 1 次提交
-
-
由 PostgreSQL Daemon 提交于
$Header: -> $PostgreSQL Changes ...
-
- 11 11月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 02 8月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
uselessly invoke it in parallel in the first place.
-
- 07 4月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
parts. Standardize spelling of comments in pg_config.h.
-
- 15 1月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
in the documentation from that same data.
-
- 14 1月, 2003 1 次提交
-
-
由 Tom Lane 提交于
source tree.
-
- 14 12月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 19 7月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
extension to create binary compatible casts. Includes dependency tracking as well. pg_proc.proimplicit is now defunct, but will be removed in a separate commit. pg_dump provides a migration path from the previous scheme to declare casts. Dumping binary compatible casts is currently impossible, though.
-
- 13 7月, 2002 1 次提交
-
-
由 Tom Lane 提交于
pg_relcheck is gone; CHECK, UNIQUE, PRIMARY KEY, and FOREIGN KEY constraints all have real live entries in pg_constraint. pg_depend exists, and RESTRICT/CASCADE options work on most kinds of DROP; however, pg_depend is not yet very well populated with dependencies. (Most of the ones that are present at this point just replace formerly hardwired associations, such as the implicit drop of a relation's pg_type entry when the relation is dropped.) Need to add more logic to create dependency entries, improve pg_dump to dump constraints in place of indexes and triggers, and add some regression tests.
-
- 11 7月, 2002 1 次提交
-
-
由 Tatsuo Ishii 提交于
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.
-
- 27 3月, 2002 1 次提交
-
-
由 Tom Lane 提交于
in schemas other than the system namespace; however, there's no search path yet, and not all operations work yet on tables outside the system namespace.
-
- 23 3月, 2002 1 次提交
-
-
由 Tom Lane 提交于
there and CREATE SCHEMA will make entries in it...
-
- 26 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
buffer manager with 'pg_clog', a specialized access method modeled on pg_xlog. This simplifies startup (don't need to play games to open pg_log; among other things, OverrideTransactionSystem goes away), should improve performance a little, and opens the door to recycling commit log space by removing no-longer-needed segments of the commit log. Actual recycling is not there yet, but I felt I should commit this part separately since it'd still be useful if we chose not to do transaction ID wraparound.
-
- 24 8月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
places that were including the wrong files.
-
- 12 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
pg_database now has unique indexes on oid and on datname. pg_shadow now has unique indexes on usename and on usesysid. pg_am now has unique index on oid. pg_opclass now has unique index on oid. pg_amproc now has unique index on amid+amopclaid+amprocnum. Remove pg_rewrite's unnecessary index on oid, delete unused RULEOID syscache. Remove index on pg_listener and associated syscache for performance reasons (caching rows that are certain to change before you need 'em again is rather pointless). Change pg_attrdef's nonunique index on adrelid into a unique index on adrelid+adnum. Fix various incorrect settings of pg_class.relisshared, make that the primary reference point for whether a relation is shared or not. IsSharedSystemRelationName() is now only consulted to initialize relisshared during initial creation of tables and indexes. In theory we might now support shared user relations, though it's not clear how one would get entries for them into pg_class &etc of multiple databases. Fix recently reported bug that pg_attribute rows created for an index all have the same OID. (Proof that non-unique OID doesn't matter unless it's actually used to do lookups ;-)) There's no need to treat pg_trigger, pg_attrdef, pg_relcheck as bootstrap relations. Convert them into plain system catalogs without hardwired entries in pg_class and friends. Unify global.bki and template1.bki into a single init script postgres.bki, since the alleged distinction between them was misleading and pointless. Not to mention that it didn't work for setting up indexes on shared system relations. Rationalize locking of pg_shadow, pg_group, pg_attrdef (no need to use AccessExclusiveLock where ExclusiveLock or even RowExclusiveLock will do). Also, hold locks until transaction commit where necessary.
-
- 15 5月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
forced.
-
- 29 10月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
a) mismatching backend program, by checking --version output b) mismatching bki files, by putting a version-identifying comment atop those files.
-
- 24 10月, 2000 1 次提交
-
-
由 Tom Lane 提交于
kibitzing from Tom Lane. Large objects are now all stored in a single system relation "pg_largeobject" --- no more xinv or xinx files, no more relkind 'l'. This should offer substantial performance improvement for large numbers of LOs, since there won't be directory bloat anymore. It'll also fix problems like running out of locktable space when you access thousands of LOs in one transaction. Also clean up cruft in read/write routines. LOs with "holes" in them (never-written byte ranges) now work just like Unix files with holes do: a hole reads as zeroes but doesn't occupy storage space. INITDB forced!
-
- 22 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
> Regression tests opr_sanity and sanity_check are now failing. Um, Bruce, I've said several times that I didn't think Perchine's large object changes should be applied until someone had actually reviewed them.
-
- 21 10月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
I tested it restoring my database with > 100000 BLOBS, and dumping it out. But unfortunatly I can not restore it back due to problems in pg_dump. -- Sincerely Yours, Denis Perchine
-
由 Peter Eisentraut 提交于
source directory. This involves mostly makefiles using $(srcdir) when they might have used ".". (Regression tests don't work with this, yet.) Sort out usage of CPPFLAGS, CFLAGS (and CXXFLAGS). Add "override" keyword in most places, to preserve necessary flags even when the user overrode the flags.
-
- 08 10月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
> this is patch v 0.4 to support transactions with BLOBs. > All BLOBs are in one table. You need to make initdb. > > -- > Sincerely Yours, > Denis Perchine
-
由 Bruce Momjian 提交于
this is patch v 0.4 to support transactions with BLOBs. All BLOBs are in one table. You need to make initdb. -- Sincerely Yours, Denis Perchine
-