hcq/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2026-03-08 13:17:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

Commit Graph

  • 3842892492 Recent changes got the sense of the notnull bit backwards in the 2.0 protocol output routines. Mea culpa :-(. Per report from Kris Jurka. Tom Lane 2005-04-23 17:45:35 +00:00
  • c114e166e5 Define the right-hand input of AT TIME ZONE as a full a_expr instead of c_expr. Perhaps the restriction was once needed to avoid bison errors, but it seems to work just fine now --- and even generates a slightly smaller state machine. This change allows examples like SELECT '13:45'::timetz AT TIME ZONE '-07:00'::interval; to work without parentheses around the right-hand input. Tom Lane 2005-04-23 17:22:16 +00:00
  • 0975b95bc3 Update FAQ release number to 8.0.2. Bruce Momjian 2005-04-23 15:22:56 +00:00
  • e947e1153a Modify output of VACUUM VERBOSE to be clearer. Bruce Momjian 2005-04-23 15:20:39 +00:00
  • ca1e578d62 int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tom Lane 2005-04-23 05:39:19 +00:00
  • c7b94bbad9 int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tom Lane 2005-04-23 05:39:01 +00:00
  • 58d0214ed8 int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tom Lane 2005-04-23 05:38:43 +00:00
  • 0548497cc5 int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tom Lane 2005-04-23 05:38:22 +00:00
  • 56c8877291 Turns out that my recent elimination of the 'redundant' flatten_andors() code in prepqual.c had a small drawback: the flatten_andors code was able to cope with deeply nested AND/OR structures (like 10000 ORs in a row), whereas eval_const_expressions tends to recurse until it overruns the stack. Revise eval_const_expressions so that it doesn't choke on deeply nested ANDs or ORs. Tom Lane 2005-04-23 04:42:53 +00:00
  • 25434e32cb Add documentation stating how to determine if FSM settings are too low --- look at a database-wide VACUUM VERBOSE. Bruce Momjian 2005-04-23 03:27:40 +00:00
  • e092828241 Teach choose_bitmap_and() to actually be choosy --- that is, try to make some estimate of which available indexes to AND together, rather than blindly taking 'em all. This could probably stand further improvement, but it seems to do OK in simple tests. Tom Lane 2005-04-23 01:57:34 +00:00
  • 4b89126ccc Fix bogus EXPLAIN display of rowcount estimates for BitmapAnd and BitmapOr nodes. Tom Lane 2005-04-23 01:29:15 +00:00
  • bc843d3960 First cut at planner support for bitmap index scans. Lots to do yet, but the code is basically working. Along the way, rewrite the entire approach to processing OR index conditions, and make it work in join cases for the first time ever. orindxpath.c is now basically obsolete, but I left it in for the time being to allow easy comparison testing against the old implementation. Tom Lane 2005-04-22 21:58:32 +00:00
  • 8e4b89ccf2 Backpatch of LIMIT / FOR UPDATE behavior, but keep pre-7.3 mention in 8.0.X. Bruce Momjian 2005-04-22 15:53:27 +00:00
  • ccbb07d922 Fix typo: Bruce Momjian 2005-04-22 15:40:16 +00:00
  • 6f61ddd40d Typo fix. Alvaro. Bruce Momjian 2005-04-22 15:32:58 +00:00
  • 5eed8ce382 Release build 216. Kris Jurka 2005-04-22 15:10:52 +00:00
  • a44f99024c Updatable ResultSets need to check for an empty ResultSet because isBeforeFirst and isAfterLast both return false for an empty result so the checking to make sure the user is on a valid row wasn't working. Kris Jurka 2005-04-22 14:48:18 +00:00
  • f5517ddbda When moveToCurrentRow is called and the current row is off the end of the ResultSet we can't try to load that row because it doesn't exist and will throw an Exception. Kris Jurka 2005-04-22 14:36:48 +00:00
  • 8f4a1b3e84 Update URL for TODO list. Bruce Momjian 2005-04-22 13:38:19 +00:00
  • d76f279a55 Remove pre-7.3 mention that FOR UPDATE can be before LIMIT. Bruce Momjian 2005-04-22 04:20:44 +00:00
  • ddae2b6801 Clarify that only crypt can't use md5 pg_shadow passwords. Bruce Momjian 2005-04-22 04:19:02 +00:00
  • 26bb65df1e Clarify that only crypt can't use md5 pg_shadow passwords. Bruce Momjian 2005-04-22 04:18:58 +00:00
  • 4f6d275ac7 Clarify use of MD5 authentication and pg_shadow encryption. Bruce Momjian 2005-04-21 22:19:27 +00:00
  • c82b895284 Clarify use of MD5 authentication and pg_shadow encryption. Bruce Momjian 2005-04-21 22:19:19 +00:00
  • 14c7fba3f7 Rethink original decision to use AND/OR Expr nodes to represent bitmap logic operations during planning. Seems cleaner to create two new Path node types, instead --- this avoids duplication of cost-estimation code. Also, create an enable_bitmapscan GUC parameter to control use of bitmap plans. Tom Lane 2005-04-21 19:18:13 +00:00
  • c6221db3c0 Updated text for bitmaps: Bruce Momjian 2005-04-21 15:20:39 +00:00
  • 631e03145f Done: Bruce Momjian 2005-04-21 04:09:34 +00:00
  • e6f7edb9d5 Install some slightly realistic cost estimation for bitmap index scans. Tom Lane 2005-04-21 02:28:02 +00:00
  • 1275ad5056 Make pg_ctl status do a kill() test to verify that the PID found in postmaster.pid still represents a live postmaster. Tom Lane 2005-04-20 23:10:22 +00:00
  • 2f8c7c866c Make pg_ctl status do a kill() test to verify that the PID found in postmaster.pid still represents a live postmaster. Tom Lane 2005-04-20 23:10:16 +00:00
  • 1c155c8dfb Add note clarifying that indexes that support ordered scans had better allow clauseless scans. Tom Lane 2005-04-20 22:19:58 +00:00
  • 6fbda16518 Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. Tom Lane 2005-04-20 21:48:39 +00:00
  • daa7e6604c Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. Tom Lane 2005-04-20 21:48:31 +00:00
  • 08008de909 Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. Tom Lane 2005-04-20 21:48:22 +00:00
  • eecc92564d Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. Tom Lane 2005-04-20 21:48:12 +00:00
  • eb4f58ad40 Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. Tom Lane 2005-04-20 21:48:04 +00:00
  • 7735c39aa0 Fix mis-display of negative fractional seconds in interval values for --enable-integer-datetimes case. Per report from Oliver Siegmar. Tom Lane 2005-04-20 17:15:19 +00:00
  • 387c398c37 Fix mis-display of negative fractional seconds in interval values for --enable-integer-datetimes case. Per report from Oliver Siegmar. Tom Lane 2005-04-20 17:15:09 +00:00
  • 25bd3019e0 Fix mis-display of negative fractional seconds in interval values for --enable-integer-datetimes case. Per report from Oliver Siegmar. Tom Lane 2005-04-20 17:14:58 +00:00
  • a8ac7d8713 Fix mis-display of negative fractional seconds in interval values for --enable-integer-datetimes case. Per report from Oliver Siegmar. Tom Lane 2005-04-20 17:14:50 +00:00
  • 9d64632144 Minor performance improvement: avoid unnecessary creation/unioning of bitmaps for multiple indexscans. Instead just let each indexscan add TIDs directly into the BitmapOr node's result bitmap. Tom Lane 2005-04-20 15:48:36 +00:00
  • de4fbfadc5 Add: Bruce Momjian 2005-04-20 02:48:11 +00:00
  • e5c7c05168 Add: Bruce Momjian 2005-04-20 02:43:49 +00:00
  • 047b8a71d1 Add: Bruce Momjian 2005-04-20 01:17:34 +00:00
  • 4a8c5d0375 Create executor and planner-backend support for decoupled heap and index scans, using in-memory tuple ID bitmaps as the intermediary. The planner frontend (path creation and cost estimation) is not there yet, so none of this code can be executed. I have tested it using some hacked planner code that is far too ugly to see the light of day, however. Committing now so that the bulk of the infrastructure changes go in before the tree drifts under me. Tom Lane 2005-04-19 22:35:18 +00:00
  • 6091d62c9d Add comment about permissions on pg_ts* tables Teodor Sigaev 2005-04-19 13:59:06 +00:00
  • 04ce41ca62 Add comment about permissions on pg_ts* tables Teodor Sigaev 2005-04-19 13:58:48 +00:00
  • cc5b676087 Add comment about permissions on pg_ts* tables Teodor Sigaev 2005-04-19 13:58:11 +00:00
  • fa66de98a9 >>>>Luckily, PG 8 is available for this. Do you have a short example? >>> >>>No, and I think it should be in the manual as an example. >>> >>>You will need to enter a loop that uses exception handling to detect >>>unique_violation. >> >>Pursuant to an IRC discussion to which Dennis Bjorklund and >>Christopher Kings-Lynne made most of the contributions, please find >>enclosed an example patch demonstrating an UPSERT-like capability. >> Bruce Momjian 2005-04-19 03:55:43 +00:00
  • bd32a25598 > >Luckily, PG 8 is available for this. Do you have a short example? > > No, and I think it should be in the manual as an example. > > You will need to enter a loop that uses exception handling to detect > unique_violation. Bruce Momjian 2005-04-19 03:37:20 +00:00
  • 7cce39c7ce The following patch should allow UPDATE_INTERVAL to be specified on the command line. We find this useful because we frequently deal with thousands of tables in an environment where neither the databases nor the tables are updated frequently. This helps allow us to cut down on the overhead of updating the list for every other primary loop of pg_autovacuum. Bruce Momjian 2005-04-19 03:35:15 +00:00
  • aa8bdab272 Attached patch gets rid of the global timezone in the following steps: Bruce Momjian 2005-04-19 03:13:59 +00:00
  • 0a2400e964 Update PITR wording, per Simon. Bruce Momjian 2005-04-19 01:40:02 +00:00
  • dd39dd232f Update PITR wording, per Simon. Bruce Momjian 2005-04-19 01:39:50 +00:00
  • 92645c42c8 pg_dumpall should enforce the server version check for itself, rather than simply passing it down to pg_dump. Else, version-related failures in pg_dumpall itself generate unhelpful error messages. Tom Lane 2005-04-18 23:48:01 +00:00
  • c822fe05ae pg_dumpall should enforce the server version check for itself, rather than simply passing it down to pg_dump. Else, version-related failures in pg_dumpall itself generate unhelpful error messages. Tom Lane 2005-04-18 23:47:52 +00:00
  • 8023b7fa5a Add WAL entry about compression. Bruce Momjian 2005-04-18 18:30:56 +00:00
  • 07dfdb8dd0 Added to TODO: Bruce Momjian 2005-04-18 18:29:57 +00:00
  • e1d55f7917 When positioned before the start of a ResultSet issuing relative(0) results in an exception being thrown when it really should be a no-op. Kris Jurka 2005-04-18 18:25:11 +00:00
  • 01979d1bd5 Update PITR setence to mention WAL and file system dump. Bruce Momjian 2005-04-18 17:40:40 +00:00
  • 1186365c3c record_in and record_recv must be careful to return a separately pfree'able result, since some callers expect to be able to pfree the result of a pass-by-reference function. Per report from Chris Trawick. Tom Lane 2005-04-18 17:11:15 +00:00
  • 7aa066f11d record_in and record_recv must be careful to return a separately pfree'able result, since some callers expect to be able to pfree the result of a pass-by-reference function. Per report from Chris Trawick. Tom Lane 2005-04-18 17:11:05 +00:00
  • d304067695 Update PITR TODO items: Bruce Momjian 2005-04-18 15:03:21 +00:00
  • 54fe332776 Update TODO script sample. Bruce Momjian 2005-04-18 14:44:04 +00:00
  • 03d712d9f4 Update for HTML markup. Bruce Momjian 2005-04-18 14:42:35 +00:00
  • 68d2f9283d Add description that WAL files used during backup have to be archived before you are done. Bruce Momjian 2005-04-18 13:11:04 +00:00
  • c68f6d7963 Add HTML version of TODO to CVS, for web site use. Bruce Momjian 2005-04-18 12:58:45 +00:00
  • 11ab2b85d7 Add HTML TODO version to CVS. Bruce Momjian 2005-04-18 12:58:11 +00:00
  • 584693cc6d Add description about partial WAL archiving for PITR: Bruce Momjian 2005-04-18 12:51:41 +00:00
  • 41d64a185e Fix html. Bruce Momjian 2005-04-18 03:46:31 +00:00
  • f1e8b57731 Test new html tag. Bruce Momjian 2005-04-18 03:17:23 +00:00
  • c57a418ce6 Add: Bruce Momjian 2005-04-18 03:00:44 +00:00
  • fef57bd487 Update PITR mention of which WAL files are needed. Bruce Momjian 2005-04-18 01:29:08 +00:00
  • d755688f24 Update PITR mention of which WAL files are needed. Bruce Momjian 2005-04-18 01:29:00 +00:00
  • db30652135 Initial implementation of lossy-tuple-bitmap data structures. Not connected to anything useful yet ... Tom Lane 2005-04-17 22:24:02 +00:00
  • 2bf3ab90bd Clarify name of file to be checked for PITR expiring. Bruce Momjian 2005-04-17 03:05:27 +00:00
  • 18b985055d Clarify name of file to be checked for PITR expiring. Bruce Momjian 2005-04-17 03:05:19 +00:00
  • 1a6ad669fb Fix comment typo. Bruce Momjian 2005-04-17 03:04:29 +00:00
  • d8b1bf4791 Create a new 'MultiExecProcNode' call API for plan nodes that don't return just a single tuple at a time. Currently the only such node type is Hash, but I expect we will soon have indexscans that can return tuple bitmaps. A side benefit is that EXPLAIN ANALYZE now shows the correct tuple count for a Hash node. Tom Lane 2005-04-16 20:07:35 +00:00
  • 85eee28cec Minor improvements to locale documentation. Tom Lane 2005-04-16 16:50:01 +00:00
  • 96d61bc163 Fix comment typo. Bruce Momjian 2005-04-15 22:49:45 +00:00
  • 5f0a974ea9 Reduce PANIC to ERROR in several xlog routines that are used in both critical and noncritical contexts (an example of noncritical being post-checkpoint removal of dead xlog segments). In the critical cases the CRIT_SECTION mechanism will cause ERROR to be promoted to PANIC anyway, and in the noncritical cases we shouldn't let an error take down the entire database. Arguably there should be *no* explicit PANIC errors in this module, only more START/END_CRIT_SECTION calls, but I didn't go that far. (Yet.) Tom Lane 2005-04-15 22:19:48 +00:00
  • 61b861421b Modify MoveOfflineLogs/InstallXLogFileSegment to avoid O(N^2) behavior when recycling a large number of xlog segments during checkpoint. The former behavior searched from the same start point each time, requiring O(checkpoint_segments^2) stat() calls to relocate all the segments. Instead keep track of where we stopped last time through. Tom Lane 2005-04-15 18:48:10 +00:00
  • beb9e2ef34 Revert addition of poorly-thought-out DUMP TIMESTAMP archive entry, which induced bug #1597 in addition to having several other misbehaviors (like labeling the dump with a completion time having nothing to do with reality). Instead just print out the desired strings where RestoreArchive was already emitting the 'PostgreSQL database dump' and 'PostgreSQL database dump complete' strings. Tom Lane 2005-04-15 16:40:59 +00:00
  • 348f856dc5 Revert addition of poorly-thought-out DUMP TIMESTAMP archive entry, which induced bug #1597 in addition to having several other misbehaviors (like labeling the dump with a completion time having nothing to do with reality). Instead just print out the desired strings where RestoreArchive was already emitting the 'PostgreSQL database dump' and 'PostgreSQL database dump complete' strings. Tom Lane 2005-04-15 16:40:36 +00:00
  • 3fa7901070 This patch changes the use of varargs.h to stdarg.h as required by modern versions of GCC. Neil Conway 2005-04-15 04:29:32 +00:00
  • ea208aca00 Remove an unused variable "waitingForSignal". From Qingqing Zhou. Neil Conway 2005-04-15 04:18:10 +00:00
  • ad9201f982 Done > * -Use indexes for MIN() and MAX() Bruce Momjian 2005-04-14 23:20:55 +00:00
  • 69cb5acf62 Make equalTupleDescs() compare attlen/attbyval/attalign rather than assuming comparison of atttypid is sufficient. In a dropped column atttypid will be 0, and we'd better check the physical-storage data to make sure the tupdescs are physically compatible. I do not believe there is a real risk before 8.0, since before that we only used this routine to compare successive states of the tupdesc for a particular relation. But 8.0's typcache.c might be comparing arbitrary tupdescs so we'd better play it safer. Tom Lane 2005-04-14 22:35:12 +00:00
  • 8e14408028 Make equalTupleDescs() compare attlen/attbyval/attalign rather than assuming comparison of atttypid is sufficient. In a dropped column atttypid will be 0, and we'd better check the physical-storage data to make sure the tupdescs are physically compatible. I do not believe there is a real risk before 8.0, since before that we only used this routine to compare successive states of the tupdesc for a particular relation. But 8.0's typcache.c might be comparing arbitrary tupdescs so we'd better play it safer. Tom Lane 2005-04-14 22:34:48 +00:00
  • 0453a997af Put back blessing of record-function tupledesc, which I removed in a fit of over-optimization. Tom Lane 2005-04-14 22:09:40 +00:00
  • aa4762e7c8 Don't try to constant-fold functions returning RECORD, since the optimizer isn't presently set up to pass them an expected tuple descriptor. Bug has been there since 7.3 but was just recently reported by Thomas Hallgren. Tom Lane 2005-04-14 21:44:46 +00:00
  • 2a35291952 Don't try to constant-fold functions returning RECORD, since the optimizer isn't presently set up to pass them an expected tuple descriptor. Bug has been there since 7.3 but was just recently reported by Thomas Hallgren. Tom Lane 2005-04-14 21:44:35 +00:00
  • 59974b0e0a Don't try to constant-fold functions returning RECORD, since the optimizer isn't presently set up to pass them an expected tuple descriptor. Bug has been there since 7.3 but was just recently reported by Thomas Hallgren. Tom Lane 2005-04-14 21:44:22 +00:00
  • 939712ee73 Don't try to constant-fold functions returning RECORD, since the optimizer isn't presently set up to pass them an expected tuple descriptor. Bug has been there since 7.3 but was just recently reported by Thomas Hallgren. Tom Lane 2005-04-14 21:44:09 +00:00
  • b79a718fac Must count '*' characters as potential arguments. Tom Lane 2005-04-14 20:53:09 +00:00
  • 055467d504 Marginal hack to use a specialized hash function for dynahash hashtables whose keys are OIDs. The only one that looks particularly performance critical is the relcache hashtable, but as long as we've got the function we may as well use it wherever it's applicable. Tom Lane 2005-04-14 20:32:43 +00:00
  • 162bd08b3f Completion of project to use fixed OIDs for all system catalogs and indexes. Replace all heap_openr and index_openr calls by heap_open and index_open. Remove runtime lookups of catalog OID numbers in various places. Remove relcache's support for looking up system catalogs by name. Bulky but mostly very boring patch ... Tom Lane 2005-04-14 20:03:27 +00:00
  • c61d1c95ea Added patch by Philip Yarra <philip.yarra@internode.on.net> for a bug in thread support. Michael Meskes 2005-04-14 10:09:20 +00:00