aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Generate a reasonable error message when an aggregate function is appliedTom Lane2000-05-26
| | | | to an undecorated relation name (cf. example from Ed Loehr, 5/25/00).
* Spell fixBruce Momjian2000-05-26
|
* More paranoia about global variables containing references to long-Tom Lane2000-05-26
| | | | since-closed file descriptors...
* After closing frontend socket, set MyProcPort->sock = -1 to ensure thatTom Lane2000-05-26
| | | | | | | | | subsequent I/O attempts fail cleanly. I'm speculating about failure scenarios in which we do pq_close, then something in a proc_exit routine opens a file (re-using that kernel FD number), then something else fails and tries to write an elog message to the frontend ... message ends up in opened file, oops. No known examples of this but it seems like a potential hole.
* Add some elog(DEBUG)'s to help diagnose mdblindwrt failures.Tom Lane2000-05-25
|
* Clean up sloppy coding of _outAExpr().Tom Lane2000-05-25
|
* Modify raw parsetree representation returned by gram.y for SubLinks:Tom Lane2000-05-25
| | | | | | | | the oper field should be a valid Node structure so it can be dumped by outfuncs.c without risk of coredump. (We had been using a raw pointer to character string, which surely is NOT a valid Node.) This doesn't cause any backwards compatibility problems for stored rules, since raw unanalyzed parsetrees are never stored.
* Do table renaming in a sane order: physical file rename must happenTom Lane2000-05-25
| | | | | | | *last*, after all updating of system catalogs. In old code, an error detected during TypeRename left the relation hosed. Also, add a call to flush the relation's relcache entry, rather than trusting to shared cache invalidation to flush it for us.
* heap_drop() should flush the relcache entry for theTom Lane2000-05-25
| | | | relation being dropped.
* Quote database name so that not-all-lowercase names are handled safely.Tom Lane2000-05-25
|
* ! * Users doing non-blocking connections need to handle the resetBruce Momjian2000-05-25
| | | | | | | ! * themselves, they'll need to check the connection status if we ! * return an error. Alfred Perlstein
* On solaris, createdb/dropdb fails because of strange behavior of system().Tatsuo Ishii2000-05-25
| | | | | (it returns error with errno ECHILD upon successful completion of commands). This fix ignores an error from system() if errno == ECHILD.
* Make the world safe for QNX's busted shell ...Tom Lane2000-05-24
|
* Make the world safe for QNX's busted shell ...Tom Lane2000-05-24
|
* add a --with-setproctitle switch to configure that leaves the use of ↵Marc G. Fournier2000-05-24
| | | | | | setproctitle() disabled by default ...
* Update so init displays status with setproctitle too, like the rest of them.Bruce Momjian2000-05-24
|
* Make setproctitle update for every query.Bruce Momjian2000-05-24
|
* Comment out no-op ps updates for setproctitle(), until we figure outBruce Momjian2000-05-23
| | | | what to do.
* comment cleanupBruce Momjian2000-05-23
|
* Fix problem in which sloppily-coded test in ExecInitIndexScan wouldTom Lane2000-05-23
| | | | | | | | | | | | think that both sides of indexqual look like index keys. An example is create table inside (f1 float8 primary key); create table outside (g1 float8, g2 float8); select * from inside,outside where f1 = atan2(g1+1, g2); ERROR: ExecInitIndexScan: both left and right ops are rel-vars (note that failure is potentially platform-dependent). Solution is a cleanup I had had in mind to make anyway: functional index keys should be represented as Var nodes in the fixed indexqual, just like regular index keys.
* Twiddle C++ configuration checks so that we #include <string> (ifTom Lane2000-05-23
| | | | | | | it exists) before testing 'using namespace std'. This is necessary on some C++ setups where the compiler won't take a 'using' until you've included a header that mentions namespace std. (Pretty braindead if you ask me, but...)
* Transmit -I switches selected by configure (particularly those fromTom Lane2000-05-23
| | | | | | --with-includes) to makefiles for pltcl and plperl, so that these switches will be used even though we do not want other top-level CFLAGS. Ain't it fun trying to support multiple-compiler platforms?
* Cast parameters to ckfree to (char *) to suppress compiler warnings.Tom Lane2000-05-23
|
* Irix fixes from Murad NayalBruce Momjian2000-05-22
|
* CleanupBruce Momjian2000-05-22
|
* I am attempting to integrate postgres (v 7.0) with an open sourceBruce Momjian2000-05-22
| | | | | | | | | | | | | | | | | | | | project I am working on (Recall - a distributed, fault-tolerant, replicated, storage framework @ http://www.fault-tolerant.org). Recall is written in C++. I need to include the postgres headers and there are some problems when including the headers w/C++. Attached is a patch generated from postgres/src that fixes my problems. I was hoping to get this into the main source. It's very small (2k) and 3 files are changed: backend/utils/fmgr/fmgr.c, backend/utils/Gen_fmgrtab.sh.in, and include/access/tupdesc.h. In C++, you get a multiply defined symbol because the variable (FmgrInfo *fmgr_pl_finfo) is defined in the header (the patch moves it to the .c file). The other problem in tupdesc.h is the use of typeid is a problem in c++ (I renamed it to oidtypeid). Thanks, Neal Norwitz
* Remove calls to getprotobyname(), which we now know leaks memory onTom Lane2000-05-21
| | | | | | some platforms --- and I also see that it is documented as not thread- safe on HPUX and possibly other platforms. No good reason not to just use IPPROTO_TCP constant from <netinet/in.h> instead.
* Repair memory leaks that caused CacheCxt to grow without bound. WeTom Lane2000-05-21
| | | | | | | | | really ought to fix relcache entry construction so that it does not do so much with CurrentMemoryContext = CacheCxt. As is, relatively harmless leaks in either sequential or index scanning translate to permanent leaks if they occur when called from relcache build. For the moment, however, the path of least resistance is to repair all such leaks...
* Add debug code to aid in memory-leak tracking: if SHOW_MEMORY_STATS isTom Lane2000-05-21
| | | | | defined then statistics about memory usage of all the global memory contexts are printed after each commit.
* Clean up grotty references to CacheCxt (externs inside functions,Tom Lane2000-05-20
| | | | duplicate global declarations, no points for style at all!)
* Enhance multibyte support.Tatsuo Ishii2000-05-20
| | | | SJIS UDC (NEC selection IBM kanji) support contributed by Eiji Tokuya
* Add KEEPALIVE option to the socket of backend. This will automaticallyTatsuo Ishii2000-05-20
| | | | terminate the backend that has no frontend anymore.
* pg_dump barfs on negative values for index column numbers --- like, say,Tom Lane2000-05-19
| | | | | an index on a table's OID column. Mea maxima culpa ... but how'd we get through beta with no one noticing this?
* Revise FlushRelationBuffers/ReleaseRelationBuffers per discussion withTom Lane2000-05-19
| | | | | | | | | | | | | | | | | | | | | Hiroshi. ReleaseRelationBuffers now removes rel's buffers from pool, instead of merely marking them nondirty. The old code would leave valid buffers for a deleted relation, which didn't cause any known problems but can't possibly be a good idea. There were several places which called ReleaseRelationBuffers *and* FlushRelationBuffers, which is now unnecessary; but there were others that did not. FlushRelationBuffers no longer emits a warning notice if it finds dirty buffers to flush, because with the current bufmgr behavior that's not an unexpected condition. Also, FlushRelationBuffers will flush out all dirty buffers for the relation regardless of block number. This ensures that pg_upgrade's expectations are met about tuple on-row status bits being up-to-date on disk. Lastly, tweak BufTableDelete() to clear the buffer's tag so that no one can mistake it for being a still-valid buffer for the page it once held. Formerly, the buffer would not be found by buffer hashtable searches after BufTableDelete(), but it would still be thought to belong to its old relation by the routines that sequentially scan the shared-buffer array. Again I know of no bugs caused by that, but it still can't be a good idea.
* Correct busted syntax of CC invocation for tas.s.Tom Lane2000-05-19
|
* Unset PGHOSTBruce Momjian2000-05-18
|
* Change remove function warning for built-ins.Bruce Momjian2000-05-18
|
* Use postmaster -i only on certain platforms.Bruce Momjian2000-05-18
|
* Throw NOTICE on built-in function removalBruce Momjian2000-05-18
|
* Add QNX localhost flag to regression testsBruce Momjian2000-05-18
|
* Fix WARN->NOTICE in docs. Change libpgeasy connection parameters to useBruce Momjian2000-05-18
| | | | PQconnectdb() style connections.
* Reduce COPY IN lock from AccessExclusive to a more reasonableTom Lane2000-05-18
| | | | | | | RowExclusive (my fault). Also, install a check to prevent people from trying COPY BINARY to stdout/from stdin. No way that will work unless we redesign the frontend COPY protocol ... which is not worth the trouble in the near future ...
* The check of class string in configure (line 1732) fails because this classBruce Momjian2000-05-17
| | | | | | | | | | | | | | | | | | | is in <string> and not in <string.h> on QNX4/egcs-2.91.60. Probably this can be changed for all platforms. The test in line 1705 uses <string> as well. Because I am not sure, I havn't this included into the patch. doc/Makefile has to be sligthly modified as it has been done for src/backend/Makefile due to a QNX4 problem (patch attached) Furthermore src/test/regress/run_check.sh needs to be patched as it has been done for regress.sh (patch attached). Please note that in the patch the postmaster is started always with the -i option. run_check.sh reports the test "limit" as failed, but in reallity it is OK. regress.sh reports it as OK. Andreas Kardos
* Back out odbc changes until 7.1.Bruce Momjian2000-05-17
|
* *** empty log message ***Michael Meskes2000-05-17
|
* Several compilation and run-time problems occur when building on SGIBruce Momjian2000-05-16
| | | | | | | | | | | | IRIX systems using the native compilers. A summary is: - Various files use "//" as a comment delimiter in c files. - Problems caused by assuming "char" is signed. cash.in: building -signed the rules regression test fails as described in FAQ_QNX4. If CHAR_MAX is "255U" then ((signed char)CHAR_MAX) is -1. postmaster.c: random number regression test failed without this change. - Some generic build issues and warning message cleanup. David Kaelbling
* Remove configure check for how to abbreviate 'tr A-Z a-z', and insteadTom Lane2000-05-16
| | | | | | | just use the portable form, tr ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz There were a bunch of places that weren't paying attention to configure's result anyway (including configure itself!?); clean them up too.
* Fixed the message Makefile produces after compiling. It still saidPeter Mount2000-05-15
| | | | | about the old Driver class, not the new package. Spotted by Joseph Shraibman <jks@p1.selectacast.net>
* cleanupBruce Momjian2000-05-15
|
* cleanupBruce Momjian2000-05-15
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-20 04:56:21 +0000