Commit Graph

  • acc4f3e3cb Update comment to mention "Name classification hierarchy" as place to check for reserved words. Bruce Momjian 2005-05-06 03:42:17 +00:00
  • 051ecca022 Remove documentation that CSV didn't handle carriage returns and line feeds properly. Bruce Momjian 2005-05-06 03:38:05 +00:00
  • 902338e06d Convert some mulit-line comments in copy.c to single line, as appropriate. Bruce Momjian 2005-05-06 02:56:42 +00:00
  • fba2a104c6 Marginal performance improvements in dynahash: make sure that everything associated with a hashtable is allocated in that hashtable's private context, so that hash_destroy only has to destroy the context and not do any retail pfree's; and tighten the inner loop of hash_seq_search. Tom Lane 2005-05-06 00:19:14 +00:00
  • 6f1ca7e457 Fix bogus hashtable setup. (This code has quite a few other problems too, but that one is in my way at the moment.) Tom Lane 2005-05-05 22:18:27 +00:00
  • 68ab4de905 Stamp release 7.2.8. Tom Lane 2005-05-05 20:10:08 +00:00
  • 07e3879c95 Stamp release 7.3.10. Tom Lane 2005-05-05 20:09:12 +00:00
  • 26f64e4c7a Stamp release 7.4.8. Tom Lane 2005-05-05 20:08:35 +00:00
  • 17eb867e98 Stamp release 8.0.3. Tom Lane 2005-05-05 20:07:36 +00:00
  • ffac21ec13 Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. Tom Lane 2005-05-05 19:54:13 +00:00
  • 5d0d60efe6 Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. Tom Lane 2005-05-05 19:54:01 +00:00
  • d9088d3071 Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. Tom Lane 2005-05-05 19:53:49 +00:00
  • 266a8975da Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. Tom Lane 2005-05-05 19:53:37 +00:00
  • c2e729fa20 Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. Tom Lane 2005-05-05 19:53:26 +00:00
  • 64c8635a4d On Win32, libintl replaces snprintf() with its own version that understands arg control, so we don't need our own. In fact, it also uses macros that conflict with ours, so we _can't_ use our own. Bruce Momjian 2005-05-05 19:15:54 +00:00
  • 160ca10609 Per core discussion, we should push out a 7.2.* release too while we are at it. Add release notes. Tom Lane 2005-05-05 17:59:40 +00:00
  • bd9b2fa84b Add comments on WSAStartup usage. Bruce Momjian 2005-05-05 16:40:42 +00:00
  • 6067403326 Add WSACleanup() for Win32 socket cleanup. Bruce Momjian 2005-05-05 16:37:04 +00:00
  • fbacd7838c Add WSACleanup() for Win32 socket cleanup. Bruce Momjian 2005-05-05 16:36:20 +00:00
  • 3731a400b4 Add WSACleanup() for Win32 socket cleanup. Bruce Momjian 2005-05-05 16:36:12 +00:00
  • d445b413c6 The issue has been raised in the past that our build system links each executable against the maximal set of libraries it might need. So for example, if one executable requires `libreadline', all executables are linked against it. Neil Conway 2005-05-05 11:50:18 +00:00
  • db70a31294 Adjust nodeBitmapIndexscan to keep the target index opened from plan startup to end, rather than re-opening it in each MultiExecBitmapIndexScan call. I had foolishly thought that opening/closing wouldn't be much more expensive than a rescan call, but that was sheer brain fade. Tom Lane 2005-05-05 03:37:23 +00:00
  • e6e7e64345 Update "control" item. Rosser Schwarz Bruce Momjian 2005-05-05 01:42:04 +00:00
  • 45c2171024 Typo fix, Dave Held Bruce Momjian 2005-05-05 01:23:51 +00:00
  • d468e19a06 Allow implicit cast from any named composite type to RECORD. At the moment this has no particular use except to allow table rows to be passed to record_out(), but that case seems to be useful in itself per recent example from Elein. Further down the road we could look at letting PL functions be declared to accept RECORD parameters. Tom Lane 2005-05-05 00:19:47 +00:00
  • b22bbd6f6e Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status, so that restart doesn't fail when old postmaster died unbetimes. Tom Lane 2005-05-04 22:35:22 +00:00
  • 13f75e378e Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status, so that restart doesn't fail when old postmaster died unbetimes. Tom Lane 2005-05-04 22:35:15 +00:00
  • a5ed98ba5a Preliminary release notes for 8.0.3, 7.4.8, 7.3.10. Tom Lane 2005-05-04 21:19:33 +00:00
  • 32083d2a5c Spell DELIMITER correctly, per Seamus Dean. Tom Lane 2005-05-04 14:25:30 +00:00
  • f593dda030 Spell DELIMITER correctly, per Seamus Dean. Tom Lane 2005-05-04 14:25:24 +00:00
  • 126eaef651 Clean up MultiXactIdExpand's API by separating out the case where we are creating a new MultiXactId from two regular XIDs. The original coding was unnecessarily complicated and didn't save any code anyway. Tom Lane 2005-05-03 19:42:41 +00:00
  • ecbc6dd3e9 Alter the signature for encoding conversion functions to declare the output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD. Tom Lane 2005-05-03 19:18:48 +00:00
  • cff25fa049 Alter the signature for encoding conversion functions to declare the output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD. Tom Lane 2005-05-03 19:18:31 +00:00
  • 4afab9639a Alter the signature for encoding conversion functions to declare the output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD. Tom Lane 2005-05-03 19:18:16 +00:00
  • 893b57c871 Alter the signature for encoding conversion functions to declare the output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD. Tom Lane 2005-05-03 19:17:59 +00:00
  • 308f01c304 Change tsearch2 to not use the unsafe practice of creating functions that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-( Tom Lane 2005-05-03 16:51:45 +00:00
  • 298e077bc4 Change tsearch2 to not use the unsafe practice of creating functions that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-( Tom Lane 2005-05-03 16:51:22 +00:00
  • 177af51c04 Change tsearch2 to not use the unsafe practice of creating functions that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-( Tom Lane 2005-05-03 16:51:00 +00:00
  • d0069f5a71 Fix a whitespace problem. From Alvaro Herrera. Dennis Bjorklund 2005-05-03 06:28:24 +00:00
  • 39e54e3208 Fix typos in documentation. Neil Conway 2005-05-03 03:10:01 +00:00
  • 47ce51c04a Add FAQ on who controls the project. Bruce Momjian 2005-05-02 20:11:27 +00:00
  • 3de0e72b56 Completed: Bruce Momjian 2005-05-02 18:27:12 +00:00
  • 76668e6eb4 Check the file system on postmaster startup and report any unreferenced files in the server log. Bruce Momjian 2005-05-02 18:26:54 +00:00
  • 323fe83608 Backport fix for correct quoting in CREATE DOMAIN example. Per Robert Treat. Neil Conway 2005-05-02 01:56:16 +00:00
  • b656150ec0 Add some missing "See Also" entries to the domain-related SQL reference pages. From Robert Treat. Neil Conway 2005-05-02 01:52:50 +00:00
  • f478856c7f Change SPI functions to use a `long' when specifying the number of tuples to produce when running the executor. This is consistent with the internal executor APIs (such as ExecutorRun), which also use a long for this purpose. It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as LONG_MAX, this wouldn't have worked on platforms where int and long are of different sizes. Per report from Tzahi Fadida. Neil Conway 2005-05-02 00:37:07 +00:00
  • 6c412f0605 Change CREATE TYPE to require datatype output and send functions to have only one argument. (Per recent discussion, the option to accept multiple arguments is pretty useless for user-defined types, and would be a likely source of security holes if it was used.) Simplify call sites of output/send functions to not bother passing more than one argument. Tom Lane 2005-05-01 18:56:19 +00:00
  • ae793ff63c Fix incorrect backslashing in regexp example, per Robert Treat. Tom Lane 2005-05-01 15:57:59 +00:00
  • 768eaf1416 Mention the actual stored size of NUMERIC values, per David Fetter. Tom Lane 2005-05-01 15:54:46 +00:00
  • 628c0893fd Remove the contents of the src/corba subdirectory: this has been dead code for a long time. Neil Conway 2005-05-01 06:15:51 +00:00
  • 7f8d2fe31c Change catalog entries for record_out and record_send to show only one argument, since that's all they are using now. Adjust type_sanity regression test so that it will complain if anyone tries to define multiple-argument output functions in future. Tom Lane 2005-04-30 20:31:39 +00:00
  • 50433d6533 Make record_out and record_send extract type information from the passed record object itself, rather than relying on a second OID argument to be correct. This patch just changes the function behavior and not the catalogs, so it's OK to back-patch to 8.0. Will remove the now-redundant second argument in pg_proc in a separate patch in HEAD only. Tom Lane 2005-04-30 20:04:46 +00:00
  • d7018abe06 Make record_out and record_send extract type information from the passed record object itself, rather than relying on a second OID argument to be correct. This patch just changes the function behavior and not the catalogs, so it's OK to back-patch to 8.0. Will remove the now-redundant second argument in pg_proc in a separate patch in HEAD only. Tom Lane 2005-04-30 20:04:33 +00:00
  • 93b2477278 Use the standard lock manager to establish priority order when there is contention for a tuple-level lock. This solves the problem of a would-be exclusive locker being starved out by an indefinite succession of share-lockers. Per recent discussion with Alvaro. Tom Lane 2005-04-30 19:03:33 +00:00
  • a4c3f7dd19 GCC 4.0 includes a new warning option, -Wformat-literal, that emits a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Neil Conway 2005-04-30 09:08:14 +00:00
  • 0d8cdcfe88 GCC 4.0 includes a new warning option, -Wformat-literal, that emits a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Neil Conway 2005-04-30 08:42:17 +00:00
  • a935e36ae9 GCC 4.0 includes a new warning option, -Wformat-literal, that emits a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Neil Conway 2005-04-30 08:36:18 +00:00
  • 757956ec47 GCC 4.0 includes a new warning option, -Wformat-literal, that emits a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Neil Conway 2005-04-30 08:19:44 +00:00
  • 47458f8c2f GCC 4.0 includes a new warning option, -Wformat-literal, that emits a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Neil Conway 2005-04-30 08:08:51 +00:00
  • 6dce59ced9 This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. Neil Conway 2005-04-30 08:01:58 +00:00
  • 8f54b05551 This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. Neil Conway 2005-04-30 08:01:29 +00:00
  • 15ea6d5a2f This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. Neil Conway 2005-04-30 08:00:55 +00:00
  • 7ce01797bd This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. Neil Conway 2005-04-30 08:00:14 +00:00
  • 16d4418bf5 Fix BCC to not define compiler location. Bruce Momjian 2005-04-30 04:00:07 +00:00
  • 23cf3986cf Update FAQ. Bruce Momjian 2005-04-30 03:53:17 +00:00
  • ef1b4fbb56 Update replication FAQ. Bruce Momjian 2005-04-30 03:52:23 +00:00
  • 3a694bb0a1 Restructure LOCKTAG as per discussions of a couple months ago. Essentially, we shoehorn in a lockable-object-type field by taking a byte away from the lockmethodid, which can surely fit in one byte instead of two. This allows less artificial definitions of all the other fields of LOCKTAG; we can get rid of the special pg_xactlock pseudo-relation, and also support locks on individual tuples and general database objects (including shared objects). None of those possibilities are actually exploited just yet, however. Tom Lane 2005-04-29 22:28:24 +00:00
  • 32d3b47e6f Remove extern from optreset that was just added. Bruce Momjian 2005-04-29 14:30:11 +00:00
  • f22b3b2760 Improve cleanup from win32 client-only build. Bruce Momjian 2005-04-29 14:07:34 +00:00
  • 930dd70992 Improve cleanup from win32 client-only build. Bruce Momjian 2005-04-29 14:07:27 +00:00
  • 5f9d19cc23 Backpatch BCC compile changes to 8.0.X for psql. Bruce Momjian 2005-04-29 13:42:24 +00:00
  • 7cebfdf211 Backpatch BCC compile changes to 8.0.X for psql. Bruce Momjian 2005-04-29 13:42:21 +00:00
  • 18b5ef5a76 This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. Neil Conway 2005-04-29 07:08:06 +00:00
  • daec16d0ba Done: Bruce Momjian 2005-04-29 05:03:02 +00:00
  • 95cb42b968 Fix Borland makefile for libpq and improve it for psql. Bruce Momjian 2005-04-29 04:21:39 +00:00
  • bedb78d386 Implement sharable row-level locks, and use them for foreign key references to eliminate unnecessary deadlocks. This commit adds SELECT ... FOR SHARE paralleling SELECT ... FOR UPDATE. The implementation uses a new SLRU data structure (managed much like pg_subtrans) to represent multiple- transaction-ID sets. When more than one transaction is holding a shared lock on a particular row, we create a MultiXactId representing that set of transactions and store its ID in the row's XMAX. This scheme allows an effectively unlimited number of row locks, just as we did before, while not costing any extra overhead except when a shared lock actually has to be shared. Still TODO: use the regular lock manager to control the grant order when multiple backends are waiting for a row lock. Tom Lane 2005-04-28 21:47:18 +00:00
  • d902e7d63b Fix a whitespace problem. From Alvaro Herrera. Dennis Bjorklund 2005-04-28 15:51:57 +00:00
  • 5de947624a Add WAL compression item to TODO.detail. Bruce Momjian 2005-04-28 13:25:40 +00:00
  • a65b1b738c Add psql \set ON_ERROR_ROLLBACK to allow statements in a transaction to error without affecting the entire transaction. Valid values are "on|interactive|off". Bruce Momjian 2005-04-28 13:09:59 +00:00
  • 115119e179 Wording improvement. Bruce Momjian 2005-04-27 20:11:11 +00:00
  • 989b55c550 Wording improvement. Bruce Momjian 2005-04-27 20:11:07 +00:00
  • 5e46908a48 Update PAM documentation, per Alvaro. Bruce Momjian 2005-04-27 20:09:58 +00:00
  • d3ee0279d6 Update PAM documentation, per Alvaro. Bruce Momjian 2005-04-27 20:09:50 +00:00
  • 46edb8efad workaround for bug in utils/date.h (timetz) Teodor Sigaev 2005-04-27 13:01:27 +00:00
  • 575d7d0330 Mention that PAM requires the user already exist in the database, per Dick Davies. Bruce Momjian 2005-04-26 03:01:22 +00:00
  • eceb05b0b9 Mention that PAM requires the user already exist in the database, per Dick Davies. Bruce Momjian 2005-04-26 03:01:09 +00:00
  • c20fb65780 On further experimentation, there were still a couple of bugs in ExpandIndirectionStar() ... and in markTargetListOrigin() too. Tom Lane 2005-04-25 22:02:30 +00:00
  • dfc5c72961 Fix ExpandIndirectionStar to handle cases where the expression to be expanded is of RECORD type, eg 'select (foo).* from (select foo(f1) from t1) ss' where foo() is a function declared with multiple OUT parameters. Tom Lane 2005-04-25 21:03:25 +00:00
  • ea19c8772e get_expr_result_type probably needs to be able to handle OpExpr as well as FuncExpr, to cover cases where a function returning tuple is invoked via an operator. Tom Lane 2005-04-25 20:59:44 +00:00
  • 73c195c607 Fix btree_gist to handle timetz zone correctly per recent changes. Tom Lane 2005-04-25 16:58:18 +00:00
  • 238fb0342e Update description: Bruce Momjian 2005-04-25 15:35:32 +00:00
  • 61cf53516e Re-add item with better description: Bruce Momjian 2005-04-25 13:03:37 +00:00
  • c5b08d3b7d Fix btree_gist to handle timetz zone correctly per recent changes. Tom Lane 2005-04-25 07:00:32 +00:00
  • a0ea71333a Avoid rechecking lossy operators twice in a bitmap scan plan. Tom Lane 2005-04-25 04:27:12 +00:00
  • 1fcd4b7a07 While determining the filter clauses for an index scan (either plain or bitmap), use pred_test to be a little smarter about cases where a filter clause is logically unnecessary. This may be overkill for the plain indexscan case, but it's definitely useful for OR'd bitmap scans. Tom Lane 2005-04-25 03:58:30 +00:00
  • 79a1b00226 Replace slightly klugy create_bitmap_restriction() function with a more efficient routine in restrictinfo.c (which can make use of make_restrictinfo_internal). Tom Lane 2005-04-25 02:14:48 +00:00
  • 7a4c34c97c Add description for concurrent sequential scans: Bruce Momjian 2005-04-25 01:42:41 +00:00
  • 5b05185262 Remove support for OR'd indexscans internal to a single IndexScan plan node, as this behavior is now better done as a bitmap OR indexscan. This allows considerable simplification in nodeIndexscan.c itself as well as several planner modules concerned with indexscan plan generation. Also we can improve the sharing of code between regular and bitmap indexscans, since they are now working with nigh-identical Plan nodes. Tom Lane 2005-04-25 01:30:14 +00:00
  • 186655e9a5 Adjust nodeBitmapIndexscan.c to not keep the index open across calls, but just to open and close it during MultiExecBitmapIndexScan. This avoids acquiring duplicate resources (eg, multiple locks on the same relation) in a tree with many bitmap scans. Also, don't bother to lock the parent heap at all here, since we must be underneath a BitmapHeapScan node that will be holding a suitable lock. Tom Lane 2005-04-24 18:16:38 +00:00
  • 8403741796 Actually, nodeBitmapIndexscan.c doesn't need to create a standard ExprContext at all, since it never evaluates any qual or tlist expressions. Tom Lane 2005-04-24 17:32:46 +00:00