hcq/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2026-04-12 00:57:01 +08:00
Code Issues Packages Projects Releases Wiki Activity

Commit Graph

  • 348b621894 Show aggregate return types in psql \da output. Magnus Hagander 2007-03-16 08:28:01 +00:00
  • 95f6d2d209 Make use of plancache module for SPI plans. In particular, since plpgsql uses SPI plans, this finally fixes the ancient gotcha that you can't drop and recreate a temp table used by a plpgsql function. Tom Lane 2007-03-15 23:12:07 +00:00
  • 6ce2ca3332 Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:49:32 +00:00
  • 5d9ce922d2 Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:49:26 +00:00
  • 328df527d6 Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:49:18 +00:00
  • 5f41ad2ccf Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:49:12 +00:00
  • aef05dbec0 Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:49:04 +00:00
  • d3ff180163 Fix a longstanding bug in VACUUM FULL's handling of update chains. The code did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). Tom Lane 2007-03-14 18:48:55 +00:00
  • 967d6add8d Arrange to install a "posixrules" entry in our timezone database, so that POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. Tom Lane 2007-03-14 17:38:29 +00:00
  • 45ca0be21b Arrange to install a "posixrules" entry in our timezone database, so that POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. Tom Lane 2007-03-14 17:38:22 +00:00
  • 1a72f357e3 Arrange to install a "posixrules" entry in our timezone database, so that POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. Tom Lane 2007-03-14 17:38:15 +00:00
  • 0169c354bf Arrange to install a "posixrules" entry in our timezone database, so that POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. Tom Lane 2007-03-14 17:38:06 +00:00
  • 754148d81f Add GIN support for pg_trgm. From Guillaume Smet <guillaume.smet@gmail.com> with minor editorization by me. Teodor Sigaev 2007-03-14 14:21:53 +00:00
  • 15f91f2789 Add GIN support for pg_trgm. From Guillaume Smet <guillaume.smet@gmail.com> with minor editorization by me. Teodor Sigaev 2007-03-14 14:15:40 +00:00
  • 547e41cdf8 Remove extra single-quotes copied from Unix build. Win32 doesn't strip single quotes... Magnus Hagander 2007-03-14 09:55:03 +00:00
  • 68a6e5e877 Fix broken markup, strange tab width. Tom Lane 2007-03-14 00:15:26 +00:00
  • 08ed6c3c5b Regression makefile now needs to make separate lists of what to clean for input/ and output/ directories, because with the addition of largeobject_1.source, they're not the same list. Apparently the current buildfarm process does not exercise whether 'make distclean' leaves a clean tree behind, else the farm would have been failing for awhile. Tom Lane 2007-03-13 22:56:48 +00:00
  • be40754e91 Rewrite win32 install documentation (it's not client only anymore, and it's now complete). Update for the MSVC6/Borland support now being only libpq. Move most of the information about full MSVC build from README file into documentation. Magnus Hagander 2007-03-13 16:03:36 +00:00
  • f4ee82e3d3 Reverted waiting for further fixes: Peter Eisentraut 2007-03-13 14:32:25 +00:00
  • f32515df77 Filter out warnings coming from the stylesheets, so that actual warnings show up properly. Show some minor progress messages. Magnus Hagander 2007-03-13 14:28:30 +00:00
  • e40889adb2 Set root of docbook stuff from buildenv.bat and not from builddoc.bat. Fix calling for file renaming when cd:ed into a different directory. Magnus Hagander 2007-03-13 09:45:32 +00:00
  • cbf1293ffd Properly use pg_strcasecmp() instead of strcasecmp(). Un-breaks win32 build. Magnus Hagander 2007-03-13 09:11:05 +00:00
  • b082ef7f12 Set stderr to unbuffered for pgbench on win32. ITAGAKI Takahiro Magnus Hagander 2007-03-13 09:06:35 +00:00
  • b9527e9840 First phase of plan-invalidation project: create a plan cache management module and teach PREPARE and protocol-level prepared statements to use it. In service of this, rearrange utility-statement processing so that parse analysis does not assume table schemas can't change before execution for utility statements (necessary because we don't attempt to re-acquire locks for utility statements when reusing a stored plan). This requires some refactoring of the ProcessUtility API, but it ends up cleaner anyway, for instance we can get rid of the QueryContext global. Tom Lane 2007-03-13 00:33:44 +00:00
  • f84308f195 Make configuration parameters fall back to their default values when they are removed from the configuration file. Peter Eisentraut 2007-03-12 22:09:28 +00:00
  • eee2289287 Make a run with perltidy to format the code. Per request from Andrew Dunstan. Magnus Hagander 2007-03-12 19:10:50 +00:00
  • 8a7b38617a Fix a race condition that caused pg_database_size() and pg_tablespace_size() to fail if an object was removed between calls to ReadDir() and stat(). Per discussion in pgsql-hackers. Alvaro Herrera 2007-03-11 06:44:11 +00:00
  • 3cda014bf4 Fix a race condition that caused pg_database_size() and pg_tablespace_size() to fail if an object was removed between calls to ReadDir() and stat(). Per discussion in pgsql-hackers. Alvaro Herrera 2007-03-11 06:43:23 +00:00
  • 576027bb3f Fix a race condition that caused pg_database_size() and pg_tablespace_size() to fail if an object was removed between calls to ReadDir() and stat(). Per discussion in pgsql-hackers. Alvaro Herrera 2007-03-11 05:22:00 +00:00
  • 5acde74e1a Add alternate result file for large object tests to handle Windows line ends. Andrew Dunstan 2007-03-10 03:42:19 +00:00
  • 5ea7b175f6 Remove unsafe calling of WSAStartup and WSACleanup from DllMain. Move the inline cleanup call around so it will be called in the right order, and be called on errors. Magnus Hagander 2007-03-08 19:27:48 +00:00
  • c0aa50630b Remove unsafe calling of WSAStartup and WSACleanup from DllMain. Move the inline cleanup call around so it will be called in the right order, and be called on errors. Magnus Hagander 2007-03-08 19:27:28 +00:00
  • 8e010acb0d Fix vac_update_relstats to ensure it always sends a relcache inval message, even if none of the fields in the pg_class row change. This behavior is necessary to ensure other backends flush rd_targblock values that might point to truncated-away pages. We got this right pre-8.2 but it was broken by overoptimistic change to not write out the pg_class row if unchanged. Per report from Pavan Deolasee. Tom Lane 2007-03-08 17:03:43 +00:00
  • 2825337232 Fix vac_update_relstats to ensure it always sends a relcache inval message, even if none of the fields in the pg_class row change. This behavior is necessary to ensure other backends flush rd_targblock values that might point to truncated-away pages. We got this right pre-8.2 but it was broken by overoptimistic change to not write out the pg_class row if unchanged. Per report from Pavan Deolasee. Tom Lane 2007-03-08 17:03:31 +00:00
  • 2b1abc8756 Athough cube is a varlena type, nowhere was a detoasting of cube's value, so fix it. Add macroses DatumGetNDBOX, PG_GETARG_NDBOX and PG_RETURN_NDBOX. Backpatch for 8.2 too. Teodor Sigaev 2007-03-07 21:25:18 +00:00
  • 2afb01dbde Athough cube is a varlena type, nowhere was a detoasting of cube's value, so fix it. Add macroses DatumGetNDBOX, PG_GETARG_NDBOX and PG_RETURN_NDBOX. Backpatch for 8.2 too. Teodor Sigaev 2007-03-07 21:21:12 +00:00
  • 626eb02198 Cleanup the bootstrap code a little, and rename "dummy procs" in the code comments and variables to "auxiliary proc", per Heikki's request. Alvaro Herrera 2007-03-07 13:35:03 +00:00
  • 9e4e0682bd Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Tom Lane 2007-03-06 22:45:41 +00:00
  • 14686de2b5 Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Tom Lane 2007-03-06 22:45:35 +00:00
  • 15c31ce09e Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Tom Lane 2007-03-06 22:45:29 +00:00
  • cafbf1e1cc Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Tom Lane 2007-03-06 22:45:23 +00:00
  • cc0cac4a49 Fix oversight in original coding of inline_function(): since check_sql_fn_retval allows binary-compatibility cases, the expression extracted from an inline-able SQL function might have a type that is only binary-compatible with the declared function result type. To avoid possibly changing the semantics of the expression, we should insert a RelabelType node in such cases. This has only been shown to have bad consequences in recent 8.1 and up releases, but I suspect there may be failure cases in the older branches too, so patch it all the way back. Per bug #3116 from Greg Mullane. Tom Lane 2007-03-06 22:45:16 +00:00
  • 46573e655f Add script to build documentation on win32 without mingw Magnus Hagander 2007-03-06 14:16:55 +00:00
  • 02284e224c Minor edits Peter Eisentraut 2007-03-06 09:59:22 +00:00
  • f12f220e5a Add more information about avoiding Linux OOM killer. Peter Eisentraut 2007-03-06 09:54:23 +00:00
  • a535cdf130 Revert temp_tablespaces because of coding problems, per Tom. Bruce Momjian 2007-03-06 02:06:15 +00:00
  • 4ae6967f5f Remove copied comments from geo_ops.c source file and replace with new comments, and cleanup functions. Remove copyright that is no longer relevant. Bruce Momjian 2007-03-05 23:29:14 +00:00
  • 37fc8a667e Remove timeline for 8.3 release, now on web site. Bruce Momjian 2007-03-05 18:04:03 +00:00
  • ef393e733e Remove old-style win32 client-only visual c++ build infrastructure for everything except libpq. We need to keep libpq to build static libraries and to use PQtrace with clients using older versions of MSVC. Magnus Hagander 2007-03-05 14:18:38 +00:00
  • e1d8deb918 Fix a typo in a comment. Heikki Linnakangas. Neil Conway 2007-03-05 14:13:12 +00:00
  • 1ae756c204 Make the newly-added regression tests for lo_truncate() consistent with the recent largeobject cosmetic fixes. Jeremy Drake. Neil Conway 2007-03-03 22:57:04 +00:00
  • 00a3807568 Cosmetic patch to large object regression test. Bruce Momjian 2007-03-03 20:17:25 +00:00
  • bc292937ae Split _bt_insertonpg to two functions. Bruce Momjian 2007-03-03 20:13:06 +00:00
  • 63c678d17b Fix for COPY-after-truncate feature. Bruce Momjian 2007-03-03 20:08:41 +00:00
  • ae35867a39 Remove undo information from pg_controldata --- never used. Bruce Momjian 2007-03-03 20:02:27 +00:00
  • 0763a56501 Add lo_truncate() to backend and libpq for large object truncation. Bruce Momjian 2007-03-03 19:52:47 +00:00
  • 90d76525c5 Add resetStringInfo(), which clears the content of a StringInfo, and fixup various places in the tree that were clearing a StringInfo by hand. Making this function a part of the API simplifies client code slightly, and avoids needlessly peeking inside the StringInfo interface. Neil Conway 2007-03-03 19:32:55 +00:00
  • 053981f405 Add logging to /contrib/pg_standby if -k couldn't clean up the log file. Bruce Momjian 2007-03-03 18:50:45 +00:00
  • e52c4a6e26 Add GUC log_lock_waits to log long wait times. Bruce Momjian 2007-03-03 18:46:40 +00:00
  • f52019cf80 Done: Bruce Momjian 2007-03-03 17:24:04 +00:00
  • df910a52a6 Allow \pset and \x, \t to use boolean constants on/off, rather than just toggle. Bruce Momjian 2007-03-03 17:19:11 +00:00
  • bb8b5b83da Update license wording in FAQ_DEV. Bruce Momjian 2007-03-03 16:12:37 +00:00
  • b7f73bedc8 Add URLs for: Bruce Momjian 2007-03-03 03:08:46 +00:00
  • 61c3e5b248 Make log_min_error_statement put LOG level at the same priority as log_min_messages does; and arrange to suppress the duplicative output that would otherwise result from log_statement and log_duration messages. Bruce Momjian and Tom Lane. Tom Lane 2007-03-02 23:37:23 +00:00
  • 1a7f6302bc HTML markup fix. Bruce Momjian 2007-03-02 21:03:55 +00:00
  • 4c644ed7b0 Fix HTML markup. Bruce Momjian 2007-03-02 21:03:11 +00:00
  • 23ef7b6cf4 in FAQ_DEV, mention we don't want non-BSD-compatible licensed patches. Bruce Momjian 2007-03-02 17:51:56 +00:00
  • 50acd427a5 Fix broken markup, improve wording. Tom Lane 2007-03-02 06:01:01 +00:00
  • fb276438b6 Suppress useless searches for unused line pointers in PageAddItem. To do this, add a 16-bit "flags" field to page headers by stealing some bits from pd_tli. We use one flag bit as a hint to indicate whether there are any unused line pointers; the remaining 15 are available for future use. Tom Lane 2007-03-02 00:48:44 +00:00
  • 3530283dae Fix miscalculation of stats collector's write delay, introduced in revision 1.117. Tom Lane 2007-03-01 20:07:02 +00:00
  • 44f72c6e9e Fix miscalculation of stats collector's write delay, introduced in revision 1.117. Tom Lane 2007-03-01 20:06:56 +00:00
  • 4edaffa1d1 Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:51:03 +00:00
  • 88d482cf86 Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:50:56 +00:00
  • 45c84659ee Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:50:49 +00:00
  • 3b14809f92 Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:50:42 +00:00
  • 44089027d5 Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:50:36 +00:00
  • cba2d2717a Fix markQueryForLocking() to work correctly in the presence of nested views. It has been wrong for this case since it was first written for 7.1 :-( Per report from Pavel Hanák. Tom Lane 2007-03-01 18:50:28 +00:00
  • 7b76bfbe18 Fix date/time formats for XML Schema output. Peter Eisentraut 2007-03-01 14:52:04 +00:00
  • 9f652d430f Fix up several contrib modules that were using varlena datatypes in not-so-obvious ways. I'm not totally sure that I caught everything, but at least now they pass their regression tests with VARSIZE/SET_VARSIZE defined to reverse byte order. Tom Lane 2007-02-28 22:44:38 +00:00
  • d1ce4f7396 Add language about rights given by posting a patch: Bruce Momjian 2007-02-28 17:28:09 +00:00
  • 2c6feff5e7 Remove temporary Windows-specific debugging code. Magnus Hagander 2007-02-28 15:59:30 +00:00
  • 234a02b2a8 Replace direct assignments to VARATT_SIZEP(x) with SET_VARSIZE(x, len). Get rid of VARATT_SIZE and VARATT_DATA, which were simply redundant with VARSIZE and VARDATA, and as a consequence almost no code was using the longer names. Rename the length fields of struct varlena and various derived structures to catch anyplace that was accessing them directly; and clean up various places so caught. In itself this patch doesn't change any behavior at all, but it is necessary infrastructure if we hope to play any games with the representation of varlena headers. Greg Stark and Tom Lane Tom Lane 2007-02-27 23:48:10 +00:00
  • 0459b591fc Update release timeline to use unnumber lists HTML. Bruce Momjian 2007-02-27 23:12:51 +00:00
  • a5f96f69cb Update DEV FAQ for CVS/SVN issue. Bruce Momjian 2007-02-27 21:07:20 +00:00
  • f7780bf391 Remove Kerberos mention in Solaris FAQ. Bruce Momjian 2007-02-27 19:10:19 +00:00
  • a5f1d6c201 Allow information schema definitions to work without requiring implicit casts to text. Peter Eisentraut 2007-02-27 18:49:43 +00:00
  • ba339f79ec Make build.bat return a proper errorcode if the build fails. Magnus Hagander 2007-02-27 15:21:48 +00:00
  • bde73ab21a Backported bug fix for #2956. Michael Meskes 2007-02-27 13:27:13 +00:00
  • e9a97570fa Backported bug fix for #2956. Michael Meskes 2007-02-27 13:27:05 +00:00
  • 278ed7c6ce Backported bug fix for #2956. Michael Meskes 2007-02-27 13:26:59 +00:00
  • b128f53343 Backported bug fix for #2956. Michael Meskes 2007-02-27 13:26:50 +00:00
  • c7ff7663e4 Get rid of the separate EState for subplans, and just let them share the parent query's EState. Now that there's a single flat rangetable for both the main plan and subplans, there's no need anymore for a separate EState, and removing it allows cleaning up some crufty code in nodeSubplan.c and nodeSubqueryscan.c. Should be a tad faster too, although any difference will probably be hard to measure. This is the last bit of subsidiary mop-up work from changing to a flat rangetable. Tom Lane 2007-02-27 01:11:26 +00:00
  • 2c47aaa0b6 Update 7.x variant horology files to match the new US DST rules. It seems likely that anyone wanting to run the regression tests in the future will have up-to-date system timezone files, so this is more likely to work than the old contents. Tom Lane 2007-02-25 22:37:06 +00:00
  • 8acd3cfb45 Update 7.x variant horology files to match the new US DST rules. It seems likely that anyone wanting to run the regression tests in the future will have up-to-date system timezone files, so this is more likely to work than the old contents. Tom Lane 2007-02-25 22:36:59 +00:00
  • 4756ff3dca Put back copyObject() call I removed in a fit of brain fade. This one is still needed despite cleanups in setrefs.c, because the point is to let the inserted Result node compute a different tlist than its input node does. Per example from Jeremy Drake. Tom Lane 2007-02-25 17:44:01 +00:00
  • 7395c76159 Update Solaris FAQ. Bruce Momjian 2007-02-23 23:22:33 +00:00
  • 655aa5b330 Now that plans have flat rangetable lists, it's a lot easier to get EXPLAIN to drill down into subplan targetlists to print the referent expression for an OUTER or INNER var in an upper plan node. Hence, make it do that always, and banish the old hack of showing "?columnN?" when things got too complicated. Tom Lane 2007-02-23 21:59:45 +00:00
  • 9cc2a71c38 Move BLCKSZ < 1024 check to guc.c. Bruce Momjian 2007-02-23 21:36:19 +00:00
  • e7aa8ab2ab Spelling fix. Bruce Momjian 2007-02-23 20:37:59 +00:00
  • 53ec43b41b Update Solaris FAQ wording, per Peter. Bruce Momjian 2007-02-23 20:30:08 +00:00