- 07 3月, 2003 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
cleaning out temp namespaces. We don't really want the server log to be cluttered with 'Drop cascades to table foo' every time someone uses a temp table...
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
> o Report server version number, database encoding, client encoding
-
由 Bruce Momjian 提交于
> o Report server version number
-
由 Bruce Momjian 提交于
< * Require DROP COLUMN CASCADE for a column that is part of a multi-column index
-
由 Bruce Momjian 提交于
> * -Modify regression tests to prevent failures do to minor numeric rounding
-
- 06 3月, 2003 5 次提交
-
-
由 Tom Lane 提交于
problems in applications that may have a large number of files open, such that libpq's socket number exceeds the range supported by fd_set. From Chris Brown.
-
由 Bruce Momjian 提交于
> o Have ALTER TABLE rename SERIAL sequences
-
由 Tom Lane 提交于
at database shutdown, and then load it again at database startup. This preserves our hard-won knowledge of free space across restarts (given an orderly shutdown, that is).
-
由 Tom Lane 提交于
DELETE with inherited target table. Fix it; add a regression test. Also, correct ancient misspelling of 'inherited'.
-
由 Tom Lane 提交于
DELETE of an inheritance tree references another inherited relation. This bug has been latent since 7.1; I'm still not quite sure why 7.1 and 7.2 don't manifest it (at least, they don't crash on a simple test case).
-
- 05 3月, 2003 1 次提交
-
-
由 Tom Lane 提交于
Adjustable threshold is gone in favor of keeping track of total requested page storage and doling out proportional fractions to each relation (with a minimum amount per relation, and some quantization of the results to avoid thrashing with small changes in page counts). Provide special- case code for indexes so as not to waste space storing useless page free space counts. Restructure internal data storage to be a flat array instead of list-of-chunks; this may cost a little more work in data copying when reorganizing, but allows binary search to be used during lookup_fsm_page_entry().
-
- 03 3月, 2003 5 次提交
-
-
由 Tom Lane 提交于
as are non-amindexnulls AMs unless first column is attnotnull.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
pg_description entries, so I did not force initdb.
-
由 Tom Lane 提交于
the join, per recent discussion on pgsql-sql. Not clear that this will come up often in real queries, but it's not any more expensive to do it right, so we may as well do it right.
-
由 Tom Lane 提交于
tupdesc even with zero tuples returned: some plpgsql routines assumed they didn't need to do SPI_freetuptable() after retrieving no tuples.
-
- 28 2月, 2003 1 次提交
-
-
由 Tom Lane 提交于
is assumed to be in local time, not GMT. This improves consistency with other operations, which all assume local timezone when it matters. Per bug #897.
-
- 27 2月, 2003 3 次提交
-
-
由 Barry Lind 提交于
Modified Files: jdbc/org/postgresql/Driver.java.in
-
由 Barry Lind 提交于
Modified Files: jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java
-
由 Barry Lind 提交于
Modified Files: jdbc/build.xml jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/PG_Stream.java jdbc/org/postgresql/errors.properties jdbc/org/postgresql/jdbc1/AbstractJdbc1Connection.java jdbc/org/postgresql/util/PSQLException.java
-
- 26 2月, 2003 2 次提交
-
-
由 D'Arcy J.M. Cain 提交于
query string. This fixes a bug where bool types sometimes returned with a string that could not be dropped into a query.
-
由 Tom Lane 提交于
recursion in RewriteQuery(); also, detect recursion in fireRIRrules(), so as to catch self-referential views per example from Ryan VanderBijl. Minor code restructuring to make it easier to catch recursive case.
-
- 25 2月, 2003 1 次提交
-
-
由 Michael Meskes 提交于
Allow whenever statement to list function without parameters.
-
- 24 2月, 2003 6 次提交
-
-
由 Tom Lane 提交于
columns. Improved version of patch by mallah@trade-india.com.
-
由 Tom Lane 提交于
end of a btree index. This isn't super-effective, since we won't move nondeletable pages, but it's better than nothing. Also, improve stats displayed during VACUUM VERBOSE.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
older than current Xmin; we don't have to wait till it's older than GlobalXmin.
-
由 Tom Lane 提交于
deleting multiple index entries on a single index page. This makes for a very substantial reduction in the amount of WAL traffic during a large delete operation.
-
由 Tom Lane 提交于
-
- 23 2月, 2003 2 次提交
-
-
由 Tom Lane 提交于
to fix, but it seems to basically work...
-
由 Tom Lane 提交于
service it until after we execute SetThisStartUpID(). Else shutdown process will write the wrong SUI into the shutdown checkpoint, which seems likely to be trouble --- although I've not quite figured out how significant it really is.
-
- 22 2月, 2003 3 次提交
-
-
由 Tom Lane 提交于
setting timezone-related variables during transaction start. They were not used anyway in platforms that HAVE_TM_ZONE or HAVE_INT_TIMEZONE, which it appears is *all* the platforms we are currently supporting. For platforms that have neither, we now only support UTC or numeric- offset-from-UTC timezones.
-
由 Tom Lane 提交于
now knows what to do upon hitting a dead page (in theory anyway, it's untested...). Add a post-VACUUM-cleanup entry point for index AMs, to provide a place for dead-page scavenging to happen. Also, fix oversight that broke btpo_prev links in temporary indexes. initdb forced due to additions in pg_am.
-
由 Tom Lane 提交于
-
- 21 2月, 2003 2 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
support btree compaction, as per proposal of a few days ago. btree index pages no longer store parent links, instead they have a level indicator (counting up from zero for leaf pages). The FixBTree recovery logic is removed, and replaced by code that detects missing parent-level insertions during WAL replay. Also, generate appropriate WAL entries when updating btree metapage and when building a btree index from scratch. I believe btree indexes are now completely WAL-legal for the first time. initdb forced due to index and WAL changes.
-
- 20 2月, 2003 1 次提交
-
-
由 Tom Lane 提交于
answer when SET TIMEZONE has been done since the start of the current transaction. Per bug report from Robert Haas. I plan some futher cleanup in HEAD, but this is a low-risk patch for the immediate issue in 7.3.
-