aboutsummaryrefslogtreecommitdiff
path: root/src/bin
Commit message (Collapse)AuthorAge
* Add a VACUUM command in hopes of making pg_upgrade usable againTom Lane1999-08-02
| | | | in MVCC environment. I do not trust this until Vadim says it's OK...
* Re-enable pg_upgrade, after adding checks that the sourceTom Lane1999-07-31
| | | | and target databases are of versions it knows about.
* Make usecatupd disabled for normal users, and allow normal users toBruce Momjian1999-07-30
| | | | update temp tables with this setting.
* While I was running some tests in psql, trying to figure out how to changeBruce Momjian1999-07-20
| | | | | | | | | | | | | | the query string to handle any length, I discovered that under certain conditions, psql will core dump when handling long strings. Thus, the patch. It was caused by a buffer overrun, probably not noticeable in a lot of cases, but pretty noticeable in mine. Problem was caused by the fact that the length check is only performed after the check for a ; to get the end of the query and execute. Cheers... MikeA
* psql fix.Bruce Momjian1999-07-19
|
* Cleanup of patch just applied.Bruce Momjian1999-07-19
|
* Set the application name, used for parsing readline's .inputrc -- dzBruce Momjian1999-07-19
| | | | Massimo
* Re-add getopt.h check, remove NT-specific tests for it.Bruce Momjian1999-07-19
|
* Move some system includes into c.h, and remove duplicates.Bruce Momjian1999-07-17
|
* More cleanupBruce Momjian1999-07-16
|
* Clean up #include in /include directory. Add scripts for checking includes.Bruce Momjian1999-07-15
|
* Fix some compiler warnings (Tomoaki Nishiyama), add WIN1250 support (Pavel ↵Tatsuo Ishii1999-07-11
| | | | Behal)
* createlang now returns 2 for language already exists.Bruce Momjian1999-07-09
|
* Remove old readme file.Bruce Momjian1999-07-05
|
* Remove QUERY_LIMIT and documenation on same. Change _ALIGN to TYPEALIGNBruce Momjian1999-06-17
| | | | for Irix.
* CleanupBruce Momjian1999-06-08
|
* Disable pg_upgrade for 6.5.Bruce Momjian1999-06-08
|
* I attach a patch for pg_upgrade. This does two things:Bruce Momjian1999-06-07
| | | | | | | | | | | 1. check whether the program is being executed in $PGDATA/.. This is necessary if the data tree is not in the standard place, as is the case with the Debian distribution (because of Debian policy). 2. give a clearer error message if the dumped data structure fails to be loaded. Oliver Elphick
* > Here is a small patch that should only affect win32 buildingBruce Momjian1999-06-07
| | | | | | | | | | | | | | | | | | | | | | > (native win32, not cygnus). > It does the following: > Patches two win32.mak files to DEFINE HAVE_VSNPRINTF and > HAVE_STRDUP. This is required to build at all. > Bumps the version number on libpq.dll from 6.4 to 6.5. > Required for install programs to work. > Adds defintions for BLCKSZ and MAXIMUM_ALIGN to "win32.h" in > the client-side libpiq directory. > > All these files are only used when building on native win32, > so it should be safe I think. > > Again, really sorry to throw this in so late, but I would > hate to do the same thing as with 6.4 (which required 6.4.1 > to at all compile on Win32). > > Thanks, > > //Magnus
* a fix for Win32 support provided by yutaka@marin.or.jp.Tatsuo Ishii1999-06-05
| | | | | The patch will avoid to add .exe suffix to the pg_encoding binary.
* Suppress indexes on large objects from psql's \d listing;Tom Lane1999-06-04
| | | | | | | | they were confusing because the large object tables themselves are not shown. (Besides, if you've got hundreds or thousands of large objects, you really don't want to see 'em at all.) Also, suppress all indexes from the \z ACL listing, since indexes have no meaningful protection information.
* Turns out OIDNAMELEN wasn't really being used at all!Tom Lane1999-06-04
| | | | Get rid of it to make customization of NAMEDATALEN easier.
* Add mention of SHARE ROW EXCLUSIVE mode.Bruce Momjian1999-06-04
|
* Thanks for this, but SET TRANSACTION ISOLATION LEVELBruce Momjian1999-06-03
| | | | | | | should be described like SET TIME ZONE: TO is not allowed, as well as DEFAULT option. There are only two forms: for Vadim.
* Add mention of FOR UPDATE and LIMIT/OFFSET>Bruce Momjian1999-06-03
|
* Update lock sgml/man/psql help pages.Bruce Momjian1999-06-03
|
* Add SET TRANSACTION ISOLATION LEVEL and SET NAMES mention.Bruce Momjian1999-06-03
|
* Update psql help so it looks better.Bruce Momjian1999-06-03
|
* Update SET commands for psql \h, man pages, and sgml.Bruce Momjian1999-06-03
|
* pg_dump failed on any database containing large objects,Tom Lane1999-06-03
| | | | | because it ignored the LOs themselves but failed to ignore the indexes on the LOs. How long has this been broken??
* Clean up uninitialized-variable warning from egcs.Tom Lane1999-05-30
| | | | (Curious that gcc doesn't complain about this code...).
* 1. Run all pg_dump queries in single serializable transaction.Vadim B. Mikheev1999-05-29
| | | | | | 2. Get rid of locking when updating statistics in vacuum. 3. Use QuerySnapshot in COPY TO and call SetQuerySnashot in main tcop loop before FETCH and COPY TO.
* Make pg_dump dump ACL's by default, print warning on use of -z, and addBruce Momjian1999-05-27
| | | | new -x option to skip acl dump.
* Fix pg_dump to use the same maximum-query-size constant asTom Lane1999-05-26
| | | | | the backend does. Remove unnecessary limitation on field size in dumpClasses_dumpData (ie, -d or -D case).
* Display numeric precision on \d.Bruce Momjian1999-05-26
|
* Allow GROUPs to be dumped properly.Bruce Momjian1999-05-26
|
* Disable use of -o and -d pg_dump options together. Can't set oids inBruce Momjian1999-05-26
| | | | inserts. Change some variables to bool to be clearer.
* Allow pg_dump -v display proper table/sequence count display.Bruce Momjian1999-05-26
|
* Make functions static or NOT_USED as appropriate.Bruce Momjian1999-05-26
|
* Another pgindent run. Sorry folks.Bruce Momjian1999-05-25
|
* pgindent run over code.Bruce Momjian1999-05-25
|
* Removed the automatic installation of built procedural languagesJan Wieck1999-05-20
| | | | | | | | | from initdb again. Added two new commands, createlang and destroylang to bin. These hopefully end this damned mklang.sql discussion. Jan
* I've got 2 pretty small patches.Bruce Momjian1999-05-15
| | | | | | | | | | configtype.patch simply fixes a typo in config.h.in pg_dump.c.patch Updates a bunch of error messages to include a reason from the backend, and also removes a couple of unnecessary if's Ole Gjerde
* Here's a small patch to cause pg_dump to emit theBruce Momjian1999-05-13
| | | | | | scale and precision for NUMERIC type column defs. Keith Parks
* Do not refer to stdin in static variable initializer ...Tom Lane1999-05-12
| | | | apparently some systems choke on that :-(.
* Added installation of created procedural languages to initdbJan Wieck1999-05-12
| | | | Jan
* Change error messages to oids come out as %u and not %d. Change has noBruce Momjian1999-05-10
| | | | real affect now.
* Allow -t tablename to preserve case if specified as "tablename".Thomas G. Lockhart1999-05-04
|
* here are some patches for 6.5.0 which I already submitted but have neverBruce Momjian1999-05-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | been applied. The patches are in the .tar.gz attachment at the end: varchar-array.patch this patch adds support for arrays of bpchar() and varchar(), which where always missing from postgres. These datatypes can be used to replace the _char4, _char8, etc., which were dropped some time ago. block-size.patch this patch fixes many errors in the parser and other program which happen with very large query statements (> 8K) when using a page size larger than 8192. This patch is needed if you want to submit queries larger than 8K. Postgres supports tuples up to 32K but you can't insert them because you can't submit queries larger than 8K. My patch fixes this problem. The patch also replaces all the occurrences of `8192' and `1<<13' in the sources with the proper constants defined in include files. You should now never find 8192 hardwired in C code, just to make code clearer. -- Massimo Dal Zotto
* psql's recognition of comments didn't work right in MULTIBYTETom Lane1999-04-25
| | | | environments; it was being careless about character lengths.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-16 05:06:49 +0000