aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Make initdb safe against usingPeter Eisentraut2000-10-28
| | | | | | a) mismatching backend program, by checking --version output b) mismatching bki files, by putting a version-identifying comment atop those files.
* Back out change to gram.y for parens.Bruce Momjian2000-10-28
|
* beos fixes from Cyril VELTERBruce Momjian2000-10-28
|
* WALVadim B. Mikheev2000-10-28
|
* Okay, here's my attempt at fixing the problems with parentheses inBruce Momjian2000-10-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | subqueries. It passes the normal 'runcheck' tests, and I've tried a few simple things like select 1 as foo union (((((select 2))))) order by foo; There are a few things that it doesn't do that have been talked about here at least a little: 1) It doesn't allow things like "IN(((select 1)))" -- the select here has to be at the top level. This is not new. 2) It does NOT preserve the odd syntax I found when I started looking at this, where a SELECT statement could begin with parentheses. Thus, (SELECT a from foo) order by a; fails. I have preserved the ability, used in the regression tests, to have a single select statement in what appears to be a RuleActionMulti (but wasn't -- the parens were part of select_clause syntax). In my version, this is a special form. This may cause some discussion: I have differentiated the two kinds of RuleActionMulti. Perhaps nobody knew there were two kinds, because I don't think the second form appears in the regression tests. This one uses square brackets instead of parentheses, but originally was otherwise the same as the one in parentheses. In this version of gram.y, the square bracket form treats SELECT statements the same as the other allowed statements. As discussed before on this list, psql cannot make sense out of the results of such a thing, but an application might. And I have designs on just such an application. ++ kevin o'gorman
* Remove compiler warnings (add missing include files). Only link againstPeter Eisentraut2000-10-28
| | | | -lm if it's actually there.
* Add --version and --help options to "postgres".Peter Eisentraut2000-10-28
|
* Make use of system-specific linker option to embed shared library searchPeter Eisentraut2000-10-27
| | | | | | path into executables and shared libraries (-rpath or -R for most). Can be disabled with --disable-rpath, since some binary packaging standards do not like this option.
* Use compiler driver, not linker, to link shared libraries on Unixware.Peter Eisentraut2000-10-27
|
* Make regression tests work with VPATH builds.Peter Eisentraut2000-10-27
|
* Fix for drop db message format changesTatsuo Ishii2000-10-27
|
* Remove gcc-only macro definitionTatsuo Ishii2000-10-27
|
* Disallow bits beyond the mask length for CIDR values, per discussionTom Lane2000-10-27
| | | | | | | on pghackers. Arrange for the sort ordering of general INET values to be network part as major sort key, host part as minor sort key. I did not force an initdb for this change, but anyone who's running indexes on general INET values may need to recreate those indexes.
* Re-implement LIMIT/OFFSET as a plan node type, instead of a hack inTom Lane2000-10-26
| | | | | | ExecutorRun. This allows LIMIT to work in a view. Also, LIMIT in a cursor declaration will behave in a reasonable fashion, whereas before it was overridden by the FETCH count.
* Fix breakage I introduced yesterday in MULTIBYTE compilations.Tom Lane2000-10-26
| | | | Sorry 'bout that, chief...
* Clean up gcc warnings in MULTIBYTE mode.Tom Lane2000-10-26
|
* Clean up broken test for whether to wait for input in SSL case.Tom Lane2000-10-25
| | | | Per discussion with Magnus Hagander.
* Ensure clause_selectivity() behaves sanely when examining an uplevel VarTom Lane2000-10-25
| | | | or a Var that references a subquery output.
* Teach psql about new relkind for views.Tom Lane2000-10-25
|
* Support SET/SHOW/RESET client_encoding and server_encoding even whenTom Lane2000-10-25
| | | | | | MULTIBYTE support is not compiled (you just can't set them to anything but SQL_ASCII). This should reduce interoperability problems between MB-enabled clients and non-MB-enabled servers.
* Minor cleanup.Tom Lane2000-10-25
|
* Synced preproc.y with gram.y.Michael Meskes2000-10-25
|
* Accept CREATE DATABASE WITH ENCODING 'SQL_ASCII' even when MULTIBYTETom Lane2000-10-25
| | | | | | support is not present. This allows a non-MB server to load a pg_dumpall script produced by an MB-enabled server, so long as only ASCII encoding was used.
* Rearrange handling of -L linker options so that they are always before allPeter Eisentraut2000-10-25
| | | | | | | the -l options. (This was not the case when using the OpenSSL or Kerberos options.) Also make sure that shared library links get to see all the -L options. Get Kerberos 5 support to compile on Redhat 7.0. Add OpenSSL and -lsocket (if used/found) to libpq link.
* From Zoltan Kovacs back in April (sorry for the delay Zoltan!):Thomas G. Lockhart2000-10-25
| | | | | | | | | | | | | | | I modified the current ODBC driver for * referential integrity error reporting, * SELECT in transactions and * disabling autocommit. I tested these changes with Borland C++ Builder -> ODBCExpress -> WinODBC driver (DLL) -> Postgres 7.0beta1 and Borland C++ Builder -> BDE -> WinODBC driver (DLL) -> Postgres 7.0beta1. The patch is based on snapshot of 22th April (I don't think that someone has modified it since that: Byron hasn't gave any sign of living for about a month and I didn't find any comments about the ODBC driver on the list).
* Final (?) fix for tar (null block at end)Philip Warner2000-10-25
| | | | Dump template db in dumpall
* Added some more C constructs to the parser.Michael Meskes2000-10-25
|
* WAL utils defsVadim B. Mikheev2000-10-25
|
* Check for SIGHUP and process config file updates just after waitingTom Lane2000-10-24
| | | | for input, not just before.
* Do not execute fastpath function calls if in transaction ABORT state.Tom Lane2000-10-24
| | | | | Just like queries, doing nothing is better than possibly getting weird error messages. Also, improve comments.
* Integer binary operators, from Marko Kreen <marko@l-t.ee>. Renamed bitxorPeter Eisentraut2000-10-24
| | | | operator to '#' for consistency. Parser still needs work.
* Fix AbortOutOfAnyTransaction logic to avoid notice aboutTom Lane2000-10-24
| | | | | | 'AbortTransaction and not in in-progress state' when client disconnects just after an error. Notice seems pretty harmless, so I'm not going to worry about back-patching this into 7.0.* ...
* Wups, messed up the comment markers on that last change.Tom Lane2000-10-24
|
* Ignore missing postmaster.opts.default file.Peter Eisentraut2000-10-24
|
* New config.guess and config.sub with Darwin support (from official GNUPeter Eisentraut2000-10-24
| | | | source). Adjust resultmap accordingly and fix some other regexps.
* Create empty file so that CVS sources compile (Vadim can fill in realTom Lane2000-10-24
| | | | definition later...)
* Update plperl README per suggestions from Edward Bridges.Tom Lane2000-10-24
|
* Enable plperl to be built when --with-perl is selected. Dunno whetherTom Lane2000-10-24
| | | | | latest fixes make it safe or not, but we won't find out if no one builds it, eh?
* Eliminate POLLUTE=1 hack for cross-Perl-version compatibility by usingTom Lane2000-10-24
| | | | Devel::PPPort instead. Thanks to Gilles Darold for doing the legwork.
* Various fixes to TAR header formatPhilip Warner2000-10-24
| | | | | Fix for endian bug in TAR output Nicer error messages in pg_dump
* WAL miscVadim B. Mikheev2000-10-24
|
* Rejigger do_lo_list's query so that obj_description() is evaluated onlyTom Lane2000-10-24
| | | | once per distinct LO, not once per pg_largeobject tuple.
* Reconsider page size for large objects: rather than stuffing disk pagesTom Lane2000-10-24
| | | | | | | | as full as possible, seems better to use a tuple size around BLCKSZ/4 so that less space is wasted when a LO tuple is updated. Also, this lets us use a logical page size that's an exact power of two, avoiding partial-page writes when client is sending us stuff in power-of-2 buffer chunks.
* Increase buffer size to improve performance of client-side lo_import.Tom Lane2000-10-24
|
* Remove arbitrary limit on number of simultaneously open large objects.Tom Lane2000-10-24
| | | | | This used to make some sense under the old implementation, but now an open LO is pretty darn cheap, so why restrict it?
* Major overhaul of large-object implementation, by Denis Perchine withTom Lane2000-10-24
| | | | | | | | | | | | | kibitzing from Tom Lane. Large objects are now all stored in a single system relation "pg_largeobject" --- no more xinv or xinx files, no more relkind 'l'. This should offer substantial performance improvement for large numbers of LOs, since there won't be directory bloat anymore. It'll also fix problems like running out of locktable space when you access thousands of LOs in one transaction. Also clean up cruft in read/write routines. LOs with "holes" in them (never-written byte ranges) now work just like Unix files with holes do: a hole reads as zeroes but doesn't occupy storage space. INITDB forced!
* Add some modicum of error detection...Tom Lane2000-10-24
|
* Remove testlo2.c --- there seems to be no difference between this andTom Lane2000-10-24
| | | | testlo.c, except it's even skimpier on error checking :-(
* If a field is incompressible ('compressed' data is actually larger thanTom Lane2000-10-23
| | | | | | | | source, due to addition of header overhead), store it as plain data rather than pseudo-compressed data. This saves a few microseconds when reading it out, but much more importantly guarantees that the toaster won't actually expand tuples that contain incompressible data. That's essential to avoid 'Tuple too big' failures with large objects.
* Polish shared library build to reduce number of special hacks. InPeter Eisentraut2000-10-23
| | | | | | | | | particular, allow linking with arbitrary commands rather than only $(AR) or $(LD), and treat C++ without hacks. Add option to disable shared libraries. This takes the place of the BSD_SHLIB variable. The regression test driver ignores the plpgsql test if there are no shared libraries available.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 12:02:01 +0000