aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* 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
|
* Fix createlang -l dbname so it works, update sgml.Bruce Momjian2000-05-15
|
* *** empty log message ***Michael Meskes2000-05-15
|
* That psql option should be --no-readline (as it used to be), not --noreadline.Peter Eisentraut2000-05-14
|
* Finally fix LISTEN problem.Bruce Momjian2000-05-14
|
* Fix create user for pgaccess.Bruce Momjian2000-05-14
|
* Tweak selectivity for area-based operators. Still a crock...Tom Lane2000-05-13
|
* Fix the off by one errors in ResultSet from 6.5.3, and more.Bruce Momjian2000-05-12
| | | | | | | | | I'm including a diff of postgresql-7.0/src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java. I've clearly marked all the fixes I did. Would *someone* who has access to the cvs please put this in? Joseph Shraibman
* This is the second time I've answered this exact same problem in twoBruce Momjian2000-05-12
| | | | | | | | | | | | | | | | | | | | | days. It seems to be a FAQ, and I think I know why. When creating a 'c' language function, CREATE FUNCTION is fed the shared object filename, and seems to succeed. Only when trying to use the function is an error thrown, by which time the coder thinks something's wrong with executing the code, not with loading it. I think I once saw it proposed to load shared objects at function creation time, but that idea was shot down on the grounds of resident memory bloat, ISTR. Here's a patch for a compromise: all it does is stat() the file, just like the loader code does, so that the errors caused by non existent files, and no directory 'x' permissions (the most common ones, it seems), get caught while the developer is still thinking about code loading. It doesn't catch all errors (like the code not being readable by the postgres user) but seems to catch the most common, without actually opening the file. What do you think? Ross
* Back out -\?. Didn't look good to Peter.Bruce Momjian2000-05-12
|
* /home/peter/commit-msgPeter Eisentraut2000-05-12
|
* Squash some more CLUSTER bugs. Never has worked on multiple-columnTom Lane2000-05-12
| | | | | | | | | | | | indexes, apparently, nor on functional indexes with more than one input column (force of natts = 1 was in the wrong branch of IF statement). Coredumped if source relation contained any uncommitted tuples, due to failure to test for success return from heap_fetch. Fetched tuple was passed directly to heap_insert, which clobbers the TID and commit status in the tuple header it's given, which meant that the source relation's tuples all got trashed as the copy proceeded. Abort partway through, and you're left with a lot of missing tuples. I wonder what else is lurking here ...
* this fixes the bug where setting the entry in he process table no longer worksMarc G. Fournier2000-05-12
| | | | | | | | under FreeBSD ... basically, if setproctitle() exists, use it ... the draw back right now is the PS_SET_STATUS stuff doesn't work, but am looking into that one right now ... at lesat now you can see who is connecting where and from where ...
* Add two checks ... one for setproctitle and one for -lutil ...Marc G. Fournier2000-05-12
| | | | Don't do anything with them at this time, but am working on that ...
* Repair list-vs-node confusion that resulted in failure for INNER JOIN ON.Tom Lane2000-05-12
| | | | | Make it behave correctly when there are more than two tables being joined, also. Update regression test expected outputs.
* Small cleanup of file.Bruce Momjian2000-05-12
|
* More psql help cleanupBruce Momjian2000-05-11
|
* Makefile CFLAGS cleanups.Bruce Momjian2000-05-11
|
* Oops, plpgsql didn't have the datetime->timestamp and timespan->intervalBruce Momjian2000-05-11
| | | | | | | mappings. In fact, it had them backward because it was using the 6.5.* code. Copied them from parser/gram.y, so it is fixed now. Looks like our first 7.0.1 fix. Oops, seems Tom has beat me to it as I was typing this.
* Fix CLUSTER ... or at least undo the bit-rot it's suffered since 6.5.Tom Lane2000-05-11
| | | | | It's still pretty fundamentally bogus :-(. Freebie side benefit: ALTER TABLE RENAME works on indexes now.
* Display -? as -\? under unix for psql.Bruce Momjian2000-05-11
|
* Add options and cleanup psql \? and -? help displaysBruce Momjian2000-05-11
|
* Update psql \? to show file rather than "fname".Bruce Momjian2000-05-09
|
* Forgot that dumpall's output script should 'delete from pg_group' beforeTom Lane2000-05-05
| | | | loading new data, for consistency with its handling of pg_shadow.
* psql: suppress warnings about too many arguments if the command is not valid ↵Peter Eisentraut2000-05-05
| | | | in the first place
* Spello SERIALIZED -> SERIALIZABLE in psql tab completionPeter Eisentraut2000-05-05
|
* ImageViewer transaction fixesPeter Mount2000-05-05
|
* Force initdb because of pg_group index fix.Tom Lane2000-05-05
|
* Make the indexes on pg_group be shared system relations.Tom Lane2000-05-05
|
* Accept pg_group as well as pg_shadow data from dumpall script.Tom Lane2000-05-05
| | | | | | Rearrange handling of VACUUMs so that they are certain to be executed as superuser not some random user; also, do not forget to vacuum template1 itself.
* Dump contents of pg_group along with pg_shadow.Tom Lane2000-05-05
|
* Don't leak a file descriptor when updating pg_pwd file. Also, check forTom Lane2000-05-04
| | | | failure of rename() call.
* Do not try to build libpq++ if class 'string' is not defined in theTom Lane2000-05-03
| | | | available C++ header files.
* Minor fixes ready for 7.0Peter Mount2000-05-03
|
* Update SCO FAQ. Billy G. AllieBruce Momjian2000-05-02
|
* Modify getdatabaseencoding(), pg_encoding_to_char()Tatsuo Ishii2000-05-02
| | | | | | pg_char_to_encoding() in multibyte disbaled case so that it does not throw an error, rather return HARD CODED default value (currently SQL_ASCII). This would solve the "non-mb backend vs. mb-enabled frontend" problem.
* Reset CurrentMemoryContext to TopMemoryContext at the beginning of errorTom Lane2000-04-30
| | | | | | | | | | | | cleanup, ie, as soon as we have caught the longjmp. This ensures that current context will be a valid context throughout error cleanup. Before it was possible that current context was pointing at a context that would get deleted during cleanup, leaving any subsequent pallocs in deep trouble. I was able to provoke an Assert failure when compiled with asserts + -DCLOBBER_FREED_MEMORY, if I did something that would cause an error to be reported by the backend large-object code, because indeed that code operates in a context that gets deleted partway through xact abort --- and CurrentMemoryContext was still pointing at it! Boo hiss.
* Remove bogus 'xid loop detected' check, which actually wasn't detectingTom Lane2000-04-30
| | | | loops, but just arbitrarily failing at 1000 locks.
* Clean up ecpg test files.Bruce Momjian2000-04-29
|
* Update pgeasy examplesBruce Momjian2000-04-28
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-23 22:09:48 +0000