7240 Commits (ae585b5c37eac14a255e4f0a544f5b9418a7bafc)

 

All Branches   

Search

Author	SHA1	Message	Date
Bruce Momjian	568df05028	Remove arrays file, already have array file.	26 years ago
Bruce Momjian	bdeeb4fe8a	Finally fix LISTEN problem.	26 years ago
Bruce Momjian	f301fabf4e	Back out listen fix.	26 years ago
Bruce Momjian	efc6b7ddfc	Update TODO list.	26 years ago
Bruce Momjian	a316339e6c	Update bug template.	26 years ago
Bruce Momjian	6dedc79b1e	Fix create user for pgaccess.	26 years ago
Tom Lane	e8e7b6305a	Tweak selectivity for area-based operators. Still a crock...	26 years ago
Bruce Momjian	2cfb14e8ea	Fix the off by one errors in ResultSet from 6.5.3, and more. ... 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	26 years ago
Bruce Momjian	a28f117790	This is the second time I've answered this exact same problem in two ... 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	26 years ago
Bruce Momjian	5e02f6b6ac	Update TODO list.	26 years ago
Bruce Momjian	e9e42f6f5f	Remove cluster TODO e-mail file	26 years ago
Bruce Momjian	40c992c7dd	Back out -\?. Didn't look good to Peter.	26 years ago
Peter Eisentraut	9d31e3a991	/home/peter/commit-msg	26 years ago
Tom Lane	475cb157b9	Squash some more CLUSTER bugs. Never has worked on multiple-column ... 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 ...	26 years ago
Marc G. Fournier	be4ae8f4b2	this fixes the bug where setting the entry in he process table no longer works ...	26 years ago
Marc G. Fournier	3383e8b828	Add two checks ... one for setproctitle and one for -lutil ... ...	26 years ago
Bruce Momjian	5160a5db0a	Update TODO list.	26 years ago
Bruce Momjian	845fb15e78	Update TODO list.	26 years ago
Tom Lane	01911c98db	Repair list-vs-node confusion that resulted in failure for INNER JOIN ON. ... Make it behave correctly when there are more than two tables being joined, also. Update regression test expected outputs.	26 years ago
Bruce Momjian	4624b84cf2	Small cleanup of file.	26 years ago
Bruce Momjian	7da0f5d7de	More psql help cleanup	26 years ago
Bruce Momjian	8101d0c571	Makefile CFLAGS cleanups.	26 years ago
Bruce Momjian	eead0e77a4	Update SGML for FETCH and url's.	26 years ago
Thomas G. Lockhart	023fdd6bbb	Fix url reference with missing fields. ... Reported by Adrian Oboroc <aoboroc@btr.md>.	26 years ago
Bruce Momjian	992e7dd4e3	Oops, plpgsql didn't have the datetime->timestamp and timespan->interval ... 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.	26 years ago
Tom Lane	37c652f89b	Fix CLUSTER ... or at least undo the bit-rot it's suffered since 6.5. ... It's still pretty fundamentally bogus :-(. Freebie side benefit: ALTER TABLE RENAME works on indexes now.	26 years ago
Bruce Momjian	e10c5597b7	Display -? as -\? under unix for psql.	26 years ago
Bruce Momjian	0fbde5d928	Add options and cleanup psql \? and -? help displays	26 years ago
Bruce Momjian	5a75ad5573	Update psql \? to show file rather than "fname".	26 years ago
Bruce Momjian	6706194e4e	Fix psql quotes in docs.	26 years ago
Bruce Momjian	3b5338da25	More single-quote fixes.	26 years ago
Bruce Momjian	4108ee962a	Add single quote.	26 years ago
Bruce Momjian	f44328b2b8	Change HISTORY to show outer joins in 7.1 or 7.2.	26 years ago
Thomas G. Lockhart	11a93191dc	Minor fixups for markup and wording.	26 years ago
Bruce Momjian	b5c430467f	Update TODO list.	26 years ago
Bruce Momjian	91885836f7	Update TODO list.	26 years ago
Bruce Momjian	50432d9d09	Update TODO list.	26 years ago
Bruce Momjian	55778b36f4	Update TODO list.	26 years ago
Tom Lane	b45f3a6e5b	Forgot that dumpall's output script should 'delete from pg_group' before ... loading new data, for consistency with its handling of pg_shadow.	26 years ago
Peter Eisentraut	5e4d8be18b	psql: suppress warnings about too many arguments if the command is not valid in the first place	26 years ago
Peter Eisentraut	8322072188	Spello SERIALIZED -> SERIALIZABLE in psql tab completion	26 years ago
Peter Mount	02faee5eaa	ImageViewer transaction fixes	26 years ago
Bruce Momjian	2937bf0adf	Update TODO list.	26 years ago
Bruce Momjian	ad1c88104b	Please apply the following patch to the FAQ_AIX ... Thanks Andreas	26 years ago
Tom Lane	0471eb1681	Because we ended up forcing an initdb for 7.0 final, we aren't going ... to need this updatepgproc.sql script after all...	26 years ago
Tom Lane	c0337ec2a9	Force initdb because of pg_group index fix.	26 years ago
Tom Lane	3bd03b3803	Make the indexes on pg_group be shared system relations.	26 years ago
Tom Lane	3a69c316cc	Accept pg_group as well as pg_shadow data from dumpall script. ... 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.	26 years ago
Tom Lane	3d1461802e	Dump contents of pg_group along with pg_shadow.	26 years ago
Tom Lane	570a58f427	Don't leak a file descriptor when updating pg_pwd file. Also, check for ... failure of rename() call.	26 years ago