- 09 10月, 1996 1 次提交
-
-
由 Bruce Momjian 提交于
No more scrolling off the screen.
-
- 08 10月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: D'Arcy Cain
-
- 07 10月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: D'Arcy Cain
-
由 Bruce Momjian 提交于
-
- 06 10月, 1996 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 05 10月, 1996 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
with some versions of sh, and a bug in the master make file that causes it to issue the message "postgres has been built" at the wrong time. Submitted by: bryanh@giraffe.netgate.net (Bryan Henderson)
-
- 03 10月, 1996 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Removed long-option names that used ${#} shell feature which was a compatability problem.
-
由 Marc G. Fournier 提交于
Submitted by: Carsten Heyl <heyl@nads.de>
-
- 24 9月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: Bruce
-
- 23 9月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
way one creates a database system. Parts that were in "make install" are not either in "make all" or initdb. Nothing goes in the PGDATA directory besides user data. Creating multiple database systems is easier. In addition to applying the patch, it is necessary to move the file libpq/pg_hba to backend/libpq/pg_hba.sample. Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
-
- 21 9月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Originally submitted by: ernst.molitor@uni-bonn.de resubmitted by: D'Arcy Cain
-
- 20 9月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
-
- 16 9月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: D'Arcy Cain
-
由 Marc G. Fournier 提交于
all the calls with strdup. Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
-
- 29 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
-
- 26 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
-
- 25 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
It adds a WITH OIDS option to the copy command, which allows dumping and loading of oids. If a copy command tried to load in an oid that is greater than its current system max oid, the system max oid is incremented. No checking is done to see if other backends are running and have cached oids. pg_dump as its first step when using the -o (oid) option, will copy in a dummy row to set the system max oid value so as rows are loaded in, they are certain to be lower than the system oid. pg_dump now creates indexes at the end to speed loading Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
-
- 21 8月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Julian Assange 提交于
-
- 20 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
-
- 14 8月, 1996 4 次提交
-
-
由 Marc G. Fournier 提交于
pg_dump and load to 2.0. I haven't gotten any feedback on whether people want it, so I am submitting it for others to decide. I would recommend an install in 1.02.1. I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was wrong. The copy is actually performed by the backend, and the 2.0 database will not be able to read 1.02.1 databases because of the new system columns. This patch does several things. It copies nulls out as \N, so they can be distinguished from '' strings. It fixes a problem where backslashes in the input stream were not output as double-backslashes. Without this patch, backslashes copied out were deleted upon input, or interpreted as special characters. Third, input is now terminated by backslash-period. This can not be part of a normal input stream. I tested this by creating a database with all sorts of nulls, backslash, and period fields and dumped the database and reloaded into a new database and compared them. Submitted by: Bruce
-
由 Marc G. Fournier 提交于
pg_dump and load to 2.0. I haven't gotten any feedback on whether people want it, so I am submitting it for others to decide. I would recommend an install in 1.02.1. I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was wrong. The copy is actually performed by the backend, and the 2.0 database will not be able to read 1.02.1 databases because of the new system columns. This patch does several things. It copies nulls out as \N, so they can be distinguished from '' strings. It fixes a problem where backslashes in the input stream were not output as double-backslashes. Without this patch, backslashes copied out were deleted upon input, or interpreted as special characters. Third, input is now terminated by backslash-period. This can not be part of a normal input stream. I tested this by creating a database with all sorts of nulls, backslash, and period fields and dumped the database and reloaded into a new database and compared them. Submitted by: Bruce
-
由 Marc G. Fournier 提交于
|We're all too familiar with psql's "no response from backend" message. |Users can't tell what this means, and psql continues prompting for |commands after it even though the backend is dead and no commands can |succeed. It eventually dies on a signal when the dead socket fills |up. I extended the message to offer a better explanation and made |psql exit when it finds the backend is dead. | |I also added a short message and newline when the user does a ctl-D so |it doesn't mess up the terminal display. | | Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
-
由 Marc G. Fournier 提交于
don't indicate that the libpq.a library is a dependency of all the /bin programs. So if the library changes, the /bin programs don't get remade. Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
-
- 13 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
does 2 things: 1) Make it hard to not notice the make failed. (As you recall, someone on the mailing list had this problem. I've had it to some extent myself). The 1.02 make files continue with the next subdirectory when a make in a subdirectory fails. The patch makes the make stop in the conventional way when a submake fails. It also adds a reassuring message when the make succeeds and adds a note to the INSTALL file to expect it. 2) Include loader flags on all invocations of the linker. The 1.02 make files omit the $(LDFLAGS) on some of the linker invocations. On my system, I need one of those flags just to make it invoke the proper version of the compiler/linker, so LDFLAGS has to be everywhere. Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
-
- 10 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
-
- 07 8月, 1996 1 次提交
-
-
由 Julian Assange 提交于
problem in psql
-
- 06 8月, 1996 1 次提交
-
-
由 Julian Assange 提交于
for slash commands)
-
- 01 8月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
Submitted by: Bruce
-
- 31 7月, 1996 3 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
In postgres95/src/backend/nodes/readfuncs, lines 1188 and 1189, local_node->relname is taken to point to a NameType, while its defined as a pointer to char. Both the casting to Name and the call of namestrcpy should, IMHO, be changed appropriately (first patch). As far as I could see from the Linux signal header file, a signal handler is declared as typedef void (*__sighandler_t)(int); Few changes to postgres95/src/backend/storage/lmgr/proc.c seem appropriate to comply with this. Finally, postgres95/src/bin/pg_version/pg_version.c defines a function GetDataHome (by default, returning an integer) and returns NULL in the function, which isn't an integer... Submitted by: ernst.molitor@uni-bonn.de
-
由 Marc G. Fournier 提交于
updates the psql.1 manual page for \ options add row count and ties it to the header option updated manual pages and comment for above change got \? to display in one screen-full (almost, \? scrolls off top) moved \r to \E, and \z to \r (for historical reasons with monitor) small code alignment cleanup Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
-
- 30 7月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
declaration is incorrect. -Kurt
-