Dear patchers,
Please find attached my first submission for installing all necessary
build files (makefile, scripts...) by default.
- for the old behavior, do a make light-install
- make install installs headers and other necessary files
such as scripts and makefiles, for postgresql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|logrotate rotates log files and hups the servers according to a
|configuration file. rotatelogs reads the log data on stdin and reopens
|a new output file once in a while. The first hunk of your patch was
|wrong, the rest seemed OK.
|
|
| OK, just
Agreed, these seem to be of general interest and have been requested in
the past. I will clean up the docs a little.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
Blah, well, guess I do need the server's address after all. The
attached patch includes:
*) inet_(client|server)_(addr|port)() and necessary documentation for
the four functions.
*) area(PATH) and documentation.
*) Checks for TEMP privs when creating objects in the temp schema
(checks for any
Bruce Momjian wrote:
I have applied the following patch with Magnus's guidance. It fixes
some Win32 problems introduced by my relative path installs.
It also removes the newline from psql for MinGW-only as posted by
Andrew. I added a mention to the Win32 todo list so we know to
remove it
Fabien COELHO [EMAIL PROTECTED] writes:
Please find attached my first submission for installing all necessary
build files (makefile, scripts...) by default.
Why? They won't do anyone any good outside the original build tree.
Even if modified so that they are useful (which is something that is
[ Use newest version.]
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Fabien COELHO
Sean Chittenden [EMAIL PROTECTED] writes:
*) inet_(client|server)_(addr|port)() and necessary documentation for
the four functions.
*) area(PATH) and documentation.
*) Checks for TEMP privs when creating objects in the temp schema
(checks for any object created in a temp namespace).
*)
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Do we know that is always true? What is the issue that 7.0 needs this
and newer released don't, and how are we sure this will not break some
strange cases in post-7.0 releases?
It's not a problem, since that code path is only ever executed
It's not a problem, since that code path is only ever executed when
dumping a 7.0 backend. It's in the MyFormatType function in pg_dump.c
that is used whenever the backend doesn't have its own format_type function.
Right. The patch looked dangerous to me too, until I understood the
context.
=?koi8-r?b?8M/UxdLRxdc=?= =?koi8-r?b?IOku5S4=?= [EMAIL PROTECTED] writes:
I tried to backport Simon Riggs patches for 7.4.x series to 7.3.x
with addition of python implementation of pg_arch.
It can be of interest if you consider to continue using 7.3 series of
postgresql.
Surely you jest.
Win32 can't have the same function coming from two library object files,
so we make is_absolute_path() a macro so libpq doesn't use path.o.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive,
*) inet_(client|server)_(addr|port)() and necessary documentation for
the four functions.
*) area(PATH) and documentation.
*) Checks for TEMP privs when creating objects in the temp schema
(checks for any object created in a temp namespace).
*) With the above change, current_user is now being used
Hi, tom
I tried to backport Simon Riggs patches for 7.4.x series to 7.3.x
with addition of python implementation of pg_arch.
It can be of interest if you consider to continue using 7.3 series of
postgresql.
Surely you jest.
Nope. We have a reason for it.
You are going to take
We need PITR, but our legacy application can't be upgraded to 7.4 Postgresql version
because of autocommit handling change. So I'll try to follow Simon development of PITR
for 7.5 PITR and backport it to 7.3.
Why not use replication instead?
Best regards
--
Command Prompt, Inc., home of
15 matches
Mail list logo
