29 Commits (42c0d1f3cd01ac737b182353934531d1fd382c80)

Author	SHA1	Message	Date
Bruce Momjian	da9a8649d8	Update copyright to 2004.	22 years ago
Tom Lane	1bf3d61504	Fix subtransaction behavior for large objects, temp namespace, files, ... password/group files. Also allow read-only subtransactions of a read-write parent, but not vice versa. These are the reasonably noncontroversial parts of Alvaro's recent mop-up patch, plus further work on large objects to minimize use of the TopTransactionResourceOwner.	22 years ago
PostgreSQL Daemon	55b113257c	make sure the $Id tags are converted to $PostgreSQL as well ...	22 years ago
Bruce Momjian	f3c3deb7d0	Update copyrights to 2003.	23 years ago
Bruce Momjian	d84fe82230	Update copyright to 2002.	24 years ago
Bruce Momjian	ea08e6cd55	New pgindent run with fixes suggested by Tom. Patch manually reviewed, ... initdb/regression tests pass.	24 years ago
Bruce Momjian	6783b2372e	Another pgindent run. Fixes enum indenting, and improves #endif ... spacing. Also adds space for one-line comments.	25 years ago
Bruce Momjian	b81844b173	pgindent run on all C files. Java run to follow. initdb/regression ... tests pass.	25 years ago
Bruce Momjian	9e1552607a	pgindent run. Make it all clean.	25 years ago
Bruce Momjian	623bf843d2	Change Copyright from PostgreSQL, Inc to PostgreSQL Global Development Group.	25 years ago
Tom Lane	a9b6b01ee8	Reconsider page size for large objects: rather than stuffing disk pages ... 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.	26 years ago
Tom Lane	4f44aa04b5	Major overhaul of large-object implementation, by Denis Perchine with ... 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!	26 years ago
Bruce Momjian	aa23c70522	BACKED OUT. ... > Regression tests opr_sanity and sanity_check are now failing. Um, Bruce, I've said several times that I didn't think Perchine's large object changes should be applied until someone had actually reviewed them.	26 years ago
Bruce Momjian	293d1e5f2c	here it is as requested by Bruce. ... I tested it restoring my database with > 100000 BLOBS, and dumping it out. But unfortunatly I can not restore it back due to problems in pg_dump. -- Sincerely Yours, Denis Perchine	26 years ago
Bruce Momjian	e5e5de8e8c	Back out: ... > this is patch v 0.4 to support transactions with BLOBs. > All BLOBs are in one table. You need to make initdb. > > -- > Sincerely Yours, > Denis Perchine	26 years ago
Bruce Momjian	cf5a950c10	Hello, ... this is patch v 0.4 to support transactions with BLOBs. All BLOBs are in one table. You need to make initdb. -- Sincerely Yours, Denis Perchine	26 years ago
Bruce Momjian	5c25d60244	Add: ... * Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.	26 years ago
Bruce Momjian	97dec77fab	Rename several destroy* functions/tags to drop*.	26 years ago
Bruce Momjian	a9591ce66a	Change #include's to use <> and "" as appropriate.	27 years ago
Bruce Momjian	6724a50787	Change my-function-name-- to my_function_name, and optimizer renames.	27 years ago
Bruce Momjian	fa1a8d6a97	OK, folks, here is the pgindent output.	28 years ago
Bruce Momjian	e0058b6172	Theses buffer leaks are caused by indexes that are kept open between ... calls. Outside a transaction, the backend detects them as buffer leaks; it sends a NOTICE, and frees them. This sometimes cause a segmentation fault (at least on Linux). These indexes are initialized on the first lo_read/lo_write/lo_tell call, and (normally) closed on a lo_close call. Thus the buffer leaks appear when lo direct access functions are used, and not with lo_import/lo_export functions (libpq version calls lo_close before ending the command, and the backend version uses another path). The included patches (against recent snapshot, and against 6.3.2) cause indexes to be closed on transaction end (that is on explicit 'END' statment, or on command termination outside trasaction blocks), thus preventing the buffer leaks while increasing performance inside transactions. Some (all?) 'classic' memory leaks are also removed. I hope it will be ok. --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr	28 years ago
Bruce Momjian	59f6a57e59	Used modified version of indent that understands over 100 typedefs.	29 years ago
Bruce Momjian	319dbfa736	Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.	29 years ago
Bruce Momjian	1ccd423235	Massive commit to run PGINDENT on all *.c and *.h files.	29 years ago
Bruce Momjian	1d8bbfd2e7	Make functions static where possible, enclose unused functions in #ifdef NOT_USED.	29 years ago
Marc G. Fournier	d2125805d1	Another directory totally cleaned out	30 years ago
Marc G. Fournier	99412aef23	remove: ... #include "postgres.h" #include "c.h"	30 years ago
Marc G. Fournier	1054097464	More cleanups of the include files ... - centralizing to simplify the -I's required to compile	30 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago