aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* It has been tested only against CVS backend, however. Some checking of theBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | | | | | | | | changes to the SQL to retrieve attributes for older versions of Postgres is probably wise. Also, please make sure that I have mapped the storage types to the correct storage names, as this is relatively poorly documented. I think that this patch might need to be considered for back-porting to 7.3.3 since at the moment, people will be losing valuable information after upgrades. Will dump: CREATE TABLE test ( a text, b text, c text, d text ); ALTER TABLE ONLY test ALTER COLUMN a SET STATISTICS 55; ALTER TABLE ONLY test ALTER COLUMN a SET STORAGE PLAIN; ALTER TABLE ONLY test ALTER COLUMN b SET STATISTICS 1000; ALTER TABLE ONLY test ALTER COLUMN c SET STORAGE EXTERNAL; ALTER TABLE ONLY test ALTER COLUMN d SET STORAGE MAIN; Christopher Kings-Lynne
* PGRES_POLLING_ACTIVE is unused, keep for backward compatibility.Bruce Momjian2003-03-20
| | | | Lennert Buytenhek
* Attached is a patch that limits the range tested by horology toBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | what is capable using integer-datatime timestamps. It does attempt to exercise the maximum allowable timestamp range. Also is a small error check when converting a timestamp from external to internal format that prevents out of range timestamps from being entered. Files patched: Index: src/backend/utils/adt/timestamp.c Added range check to prevent out of range timestamps from being used. Index: src/test/regress/sql/horology.sql Index: src/test/regress/expected/horology-no-DST-before-1970.out Index: src/test/regress/expected/horology-solaris-1947.out Limited range of timestamps being checked to Jan 1, 4713 BC to Dec 31, 294276 In creating this patch, I have seen some definite problems with integer timestamps and how they react when used near their limits. For example, the following statement gives the correct result: SELECT timestamp without time zone 'Jan 1, 4713 BC' + interval '109203489 days' AS "Dec 31, 294276"; However, this statement which is the logical inverse of the above gives incorrect results: SELECT timestamp without time zone '12/31/294276' - timestamp without time zone 'Jan 1, 4713 BC' AS "109203489 Days"; John Cochran
* Here's some changes I made last night to psql's common.c (as found inBruce Momjian2003-03-20
| | | | | | | | | 7.3.2). It removes some code duplication and #ifdeffing, and some unstructured ugliness such as tacky breaks and an unneeded continue. Breaks up a large function into smaller functions and reduces required nesting levels, and kills a variable or two. Jeroen T. Vermeulen
* Peter found bug in the to_char() routine for PL/MI options. ThisBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | patch fix it -- but this patch doesn't contains tests or docs fixes. I will send it later. Fixed outputs: select to_char(x, '9999.999') as x, to_char(x, 'S9999.999') as s, to_char(x, 'SG9999.999') as sg, to_char(x, 'MI9999.999') as mi, to_char(x, 'PL9999.999') as pl, to_char(x, 'PLMI9999.999') as plmi, to_char(x, '9999.999SG') as sg2, to_char(x, '9999.999PL') as pl2, to_char(x, '9999.999MI') as mi2 from num; Karel Zak
* > > - Move SEQ_MAXVALUE, SEQ_MINVALUE definitions to sequence.hBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > > > - Add check in pg_dump to see if the value returned is the max /min > > values and replace with NO MAXVALUE, NO MINVALUE. > > > > - Change START and INCREMENT to use START WITH and INCREMENT BY syntax. > > This makes it a touch easier to port to other databases with sequences > > (Oracle). PostgreSQL supports both syntaxes already. > > + char bufm[100], > + bufx[100]; > > This seems to be an arbitary size. Why not set it to the actual maximum > length? > > Also: > > + snprintf(bufm, 100, INT64_FORMAT, SEQ_MINVALUE); > + snprintf(bufx, 100, INT64_FORMAT, SEQ_MAXVALUE); > > sizeof(bufm), sizeof(bufx) is probably the more > maintenance-friendly/standard way to do it. I changed the code to use sizeof - but will wait for a response from Peter before changing the size. It's consistent throughout the sequence code to be 100 for this purpose. Rod Taylor <rbt@rbt.ca>
* "Information_schema" changesBruce Momjian2003-03-20
| | | | | | | | | - Add domain check constraints to "check_constraints" view - Create "domains" view - Create "domain_constraints" view -- Rod Taylor <rbt@rbt.ca>
* (Now featuring documentation: fixed some typos, expanded theBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | Envrironment and Files section, explained exactly what -w does) This is a patch which allows pg_ctl to make an intelligent guess as to the proper port when running 'psql -l' to determine if the database has started up (the -w flag). The environment variable PGPORT is used. If that is not found, it checks if a specific port has been set inside the postgresql.conf file. If it is has not, it uses the port that Postgres was compiled with. Greg Sabino Mullane greg@turnstep.com
* This trivial cleans up a little bit of the code inBruce Momjian2003-03-20
| | | | | | | src/test/regress/regress.c (e.g. removing K & R style parameter declarations, improving sprintf() usage, etc.) Neil Conway
* > I can see a couple possible downsides: (a) the library might have someBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | | | | | > weird behavior across fork boundaries; (b) the additional memory space > that has to be duplicated into child processes will cost something per > child launch, even if the child never uses it. But these are only > arguments that it might not *always* be a prudent thing to do, not that > we shouldn't give the DBA the tool to do it if he wants. So fire away. Here is a patch for the above, including a documentation update. It creates a new GUC variable "preload_libraries", that accepts a list in the form: preload_libraries = '$libdir/mylib1:initfunc,$libdir/mylib2' If ":initfunc" is omitted or not found, no initialization function is executed, but the library is still preloaded. If "$libdir/mylib" isn't found, the postmaster refuses to start. In my testing with PL/R, it reduces the first call to a PL/R function (after connecting) from almost 2 seconds, down to about 8 ms. Joe Conway
* > Mph. It fails for me too when I use --enable-integer-datetimes. LooksBruce Momjian2003-03-20
| | | | | | | | | | | | | | | | | | | | | | | > like that patch still needs some work... Yeah. I'm really, really, *really* sorry for submitting it in the state it was in. I shouldn't have done that just before moving to another country. I found the problem last night, but couldn't get to a Net connection until now. The problem is in src/bin/psql/common.c, around line 250-335 somewhere depending on the version. The 2nd and 3rd clauses of the "while" loop condition: (rstatus == PGRES_COPY_IN) && (rstatus == PGRES_COPY_OUT)) should of course be: (rstatus != PGRES_COPY_IN) && (rstatus != PGRES_COPY_OUT)) Jeroen T. Vermeulen
* Minor doc patch: create functionBruce Momjian2003-03-20
| | | | Gavin Sherry
* Just some fixups to a couple contrib directories I was trying out.Bruce Momjian2003-03-20
| | | | | | | | | . replace CREATE OR REPLACE AGGREGATE with a separate DROP and CREATE . add DROP for all CREATE OPERATORs . use IMMUTABLE and STRICT instead of WITH (isStrict) . add IMMUTABLE and STRICT to int_array_aggregate's accumulator function Gregory Stark
* The attatched patch fixes a memory error with contrib/dbmirror/pending.cBruce Momjian2003-03-20
| | | | | | | | when running it with older(Pre 7.3.x) versions of Postgresql. Backpatched to 7.3.X. Steven Singer
* Item done:Bruce Momjian2003-03-20
| | | | > * -Add start time to pg_stat_activity
* Add start time to pg_stat_activityBruce Momjian2003-03-20
| | | | Neil Conway
* This patch fixes a very small memory leak in psql, spotted withBruce Momjian2003-03-19
| | | | | | valgrind. Neil Conway
* Remove typecasting section that isn't needed anymore.Bruce Momjian2003-03-19
|
* Set up the privileges on the default schemas in initdb with real GRANTPeter Eisentraut2003-03-19
| | | | commands, to arrive at a valid and dumpable state.
* Avoid mysterious warning about possibly uninitialized variable.Peter Eisentraut2003-03-19
|
* Applied patch to work around server bug.Barry Lind2003-03-19
| | | | | Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1Connection.java
* Fix typo:Bruce Momjian2003-03-19
| | | | | < * Rod is Rod Taylor <pg@rbt.ca)> > * Rod is Rod Taylor <pg@rbt.ca>
* Reimplement create and drop scripts in C, to reduce repetitivePeter Eisentraut2003-03-18
| | | | | connections, increase robustness, add NLS, and prepare for Windows port. (vacuumdb and clusterdb will follow later.)
* Make the printing code somewhat more independent by not relying onPeter Eisentraut2003-03-18
| | | | | functions and global variables from the rest of psql. Also clean up some data type mismatches created by the last pager patch.
* Improve error message.Peter Eisentraut2003-03-18
|
* Fix off-by-one error in the maxlen parameter handling.Peter Eisentraut2003-03-18
|
* Compiling anything that uses InvalidOid under g++ yields a warning aboutBruce Momjian2003-03-18
| | | | | | | the expression using an "old-style cast." Therefore, would it be okay to patch postgres_ext.h as follows: Jeroen T. Vermeulen
* Remove duplicate ANALYZE recommendation in pg_dump.Bruce Momjian2003-03-18
|
* Some bugfixes for numerical library.Michael Meskes2003-03-18
|
* Applied updated translation patchBarry Lind2003-03-18
| | | | | Modified Files: errors_zh_TW.properties
* Add to mmap discussion.Bruce Momjian2003-03-18
|
* Add mention of ANALYZE after object restore.Bruce Momjian2003-03-18
|
* Add mention of new sets returning functions capability.Bruce Momjian2003-03-17
|
* Update links, from Ian BarwickBruce Momjian2003-03-17
|
* Add:Bruce Momjian2003-03-17
| | | | > * Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple columns
* Reorder crypt.h include for SunOS compile problem.Bruce Momjian2003-03-17
| | | | Fred Houweling
* Increase max known database size.Bruce Momjian2003-03-17
|
* Forgot some files...Michael Meskes2003-03-16
|
* Started working on a seperate pgtypes library. First test work. PLEASE test ↵Michael Meskes2003-03-16
| | | | compilation on iother systems.
* Arrange to print the relevant key values when reporting a foreign-keyTom Lane2003-03-15
| | | | | violation. Also, factor out some duplicate code in the RI triggers. Patch by Dmitry Tkach, reviewed by Stephan Szabo and Tom Lane.
* A typo in src/backend/libpq/hba.c breaks local ident authenticationBruce Momjian2003-03-15
| | | | | | | in the SO_PEERCRED case. elif is misspelled as elsif for the test. A patch is attached. Bruno Wolff III
* pg_dumpall failed on groups having no members. Per report fromTom Lane2003-03-14
| | | | Nick Eskelinen.
* Remove unneeded dash blocks around function start comments.Bruce Momjian2003-03-14
|
* Update name of GUC var:Bruce Momjian2003-03-14
| | | | | < * Add GUC log_statement_duration to print statement and >= min duration > * Add GUC log_statement_and_duration to print statement and >= min duration
* Add:Bruce Momjian2003-03-14
| | | | > * Add GUC log_statement_duration to print statement and >= min duration
* Fixed parsing to handle \n for updateable result sets. Bug reported by Rich ↵Barry Lind2003-03-14
| | | | | | | Cullingford. Modified Files: jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java
* Repair incorrect prorettype entry for timestamptz_izone. Can't forceTom Lane2003-03-14
| | | | | initdb in the 7.3 branch, but we can at least make it right for people who install 7.3.3 from scratch.
* Improved error message and added some log messages in batch update functionalityBarry Lind2003-03-14
| | | | | | | Modified Files: jdbc/org/postgresql/errors.properties jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java jdbc/org/postgresql/util/PSQLException.java
* Make eval_const_expressions simplify FieldSelect from a whole-row VarTom Lane2003-03-14
| | | | into an ordinary one-field Var. Per example from Chris Mungall.
* Prevent infinite loop in ln_var() due to roundoff error.Tom Lane2003-03-14
| | | | Per report from Dave Marin.