aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Make sure targetlist generated for subplan does not shareTom Lane1999-05-04
| | | | | nodes with HAVING qualifier of upper plan. Have not seen any failures, just being a little bit paranoid...
* Correct declaration of array_map() so that it doesn't makeTom Lane1999-05-03
| | | | gcc quite so unhappy.
* here are some patches for 6.5.0 which I already submitted but have neverBruce Momjian1999-05-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | been applied. The patches are in the .tar.gz attachment at the end: varchar-array.patch this patch adds support for arrays of bpchar() and varchar(), which where always missing from postgres. These datatypes can be used to replace the _char4, _char8, etc., which were dropped some time ago. block-size.patch this patch fixes many errors in the parser and other program which happen with very large query statements (> 8K) when using a page size larger than 8192. This patch is needed if you want to submit queries larger than 8K. Postgres supports tuples up to 32K but you can't insert them because you can't submit queries larger than 8K. My patch fixes this problem. The patch also replaces all the occurrences of `8192' and `1<<13' in the sources with the proper constants defined in include files. You should now never find 8192 hardwired in C code, just to make code clearer. -- Massimo Dal Zotto
* Revise union_planner and associated routines to clean up breakageTom Lane1999-05-03
| | | | | from EXCEPT/HAVING patch. Cases involving nontrivial GROUP BY expressions now work again. Also, the code is at least somewhat better documented...
* Clean up cost_sort some more: most callers were double-countingTom Lane1999-05-01
| | | | the cost of reading the source data.
* Arrange for VACUUM to delete the init file that relcache.c usesTom Lane1999-05-01
| | | | | | to save a little bit of backend startup time. This way, the first backend started after a VACUUM will rebuild the init file with up-to-date statistics for the critical system indexes.
* -T was omitted from getopt() call.Tom Lane1999-05-01
|
* Fix compile failures in dt.c --- line broken in middle ofTom Lane1999-05-01
| | | | an identifier :-(. Sloppy transmission of a patch, likely.
* Patch from "Hiroshi Inoue" <Inoue@tpf.co.jp> forVadim B. Mikheev1999-05-01
| | | | FATAL 1:btree: BTP_CHAIN flag was expected
* Use page-level ExtendLock lock instead of table-level -Vadim B. Mikheev1999-05-01
| | | | should be faster.
* cleanupBruce Momjian1999-04-30
|
* Clean up typo causing compile failure.Bruce Momjian1999-04-30
|
* Fill in reasonable-looking cost estimates in inserted nodes.Tom Lane1999-04-30
| | | | | This makes no difference to the optimizer, which has already decided what it's gonna do, but it makes the output of EXPLAIN much more plausible.
* Clean up some bogosities in path cost estimation, likeTom Lane1999-04-30
| | | | | sometimes estimating an index scan of a table to be cheaper than a sequential scan of the same tuples...
* Fix nasty little typo that prevented get_cheapest_path_for_joinkeysTom Lane1999-04-30
| | | | | from ever returning a path. This put a bit of a crimp in the system's ability to generate intelligent merge-join plans...
* Prevent priority inversion in locking by checking for existing locksBruce Momjian1999-04-30
| | | | before going into queue behind person with higher piority.
* Bugfix (bug by me in 1.4) in backparsing INSERT ... SELECTJan Wieck1999-04-29
| | | | Jan
* Defend against 'update oid'. Someday we might want to supportTom Lane1999-04-29
| | | | | that, but it'd be a New Feature, wouldn't it ... in the meantime, avoiding a backend crash seems worthwhile.
* Aggregate functions didn't work on subscripted array references.Tom Lane1999-04-29
| | | | Things are better now.
* Several routines in setrefs.c would crash on array refsTom Lane1999-04-29
| | | | due to lack of check for recursing into a null subexpression.
* Fix stupid typo that broke empty-query response... odd thatTom Lane1999-04-28
| | | | this is not revealed by any of our regression tests...
* Fixed DECIMAL data type to handle specified precision in atttypmodJan Wieck1999-04-27
| | | | Jan
* Fix for _copyUnique() suggested by Hiroshi InoueTatsuo Ishii1999-04-27
|
* These are no longer used ...Marc G. Fournier1999-04-26
|
* provides string to be used for expected/* files for system specific output...Marc G. Fournier1999-04-26
|
* *** empty log message ***Michael Meskes1999-04-26
|
* Fix from Yutaka Tanida <yutaka@marin.or.jp> for Cygwin32 support.Tatsuo Ishii1999-04-26
|
* Fix from Yutaka Tanida <yutaka@marin.or.jp>Tatsuo Ishii1999-04-26
|
* Insert a test for missing targetlist entry in replace_agg_clause.Tom Lane1999-04-26
|
* It looks like the multibyte regress tests only work if bothTom Lane1999-04-25
| | | | | | | the database encoding and the client encoding match the encoding expected by the test. So, force both of them to be set from the MULTIBYTE environment var. This allows regress tests to be run successfully in multibyte environments other than the compiled-in default.
* More multibyte tests with obsolete spelling of error message...Tom Lane1999-04-25
|
* psql's recognition of comments didn't work right in MULTIBYTETom Lane1999-04-25
| | | | environments; it was being careless about character lengths.
* Explicitly set PGCLIENTENCODING during regression tests,Tom Lane1999-04-25
| | | | since multibyte tests fail if it's different from database...
* Still had a few MULTIBYTE problems when client encoding wasTom Lane1999-04-25
| | | | different from database's ...
* Correct potential infinite loop in pg_utf2wchar_with_len;Tom Lane1999-04-25
| | | | | | it failed to cover the case where high bits of char are 100 or 101. Not sure if fix is right, but it agrees with pg_utf_mblen ... and it doesn't lock up ...
* Multibyte tests were all 'failing' because of change ofTom Lane1999-04-25
| | | | | wording of 'relation does not exist' error message. Update expected files accordingly.
* My first cut at libpq revision didn't handle MULTIBYTE correctly,Tom Lane1999-04-25
| | | | but I think it's OK now...
* Clean up gcc warning in MULTIBYTE code.Tom Lane1999-04-25
|
* ifdef out some unused routines to suppress gcc warnings.Tom Lane1999-04-25
|
* Ooops, missed committing this one...Tom Lane1999-04-25
|
* Revise backend libpq interfaces so that messages to the frontendTom Lane1999-04-25
| | | | | | can be generated in a buffer and then sent to the frontend in a single libpq call. This solves problems with NOTICE and ERROR messages generated in the middle of a data message or COPY OUT operation.
* Rename explain's "size" to "rows".Bruce Momjian1999-04-23
|
* Add disk space message to "can not extend" message.Bruce Momjian1999-04-23
|
* Remove "Non-functional update" notices since that message has beenThomas G. Lockhart1999-04-23
| | | | disabled (commented-out) in the code.
* Repair missing heap_endscan() in OperatorUpd().Tom Lane1999-04-23
|
* Fix duplicating ROOT page in concurrent updates.Vadim B. Mikheev1999-04-22
|
* Un-break CREATE TYPE. Fix some other inconsistencies in theTom Lane1999-04-20
| | | | | pg_proc entries for array I/O routines besides the one detected by the original patcher. Tighten type_sanity regress test accordingly.
* Change elog(ERROR) to get back to main loop via a plain sigsetjmp,Tom Lane1999-04-20
| | | | | | instead of doing a kill(self, SIGQUIT) and expecting the signal handler to do it. Also, clean up inconsistent definitions of the sigjmp buffer in the several files that already referenced it.
* Portability patches for HPUX 11 and Unixware in configureTom Lane1999-04-20
| | | | | | and related files. Also remove float.c's gratuitous redeclaration of isinf() ... looks like there are more decls in there that ought to be in config.h, but I'll leave well enough alone for now ...
* Add temporary for temp.Bruce Momjian1999-04-19
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 00:50:22 +0000