add boolean option --temp-keep to pg_regress to keep the existing
tmp_check installation, instead of overwriting it with a fresh make
install. Useful to test minor modifications in the current tmp_check
installation.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
*** src/test/regress/pg_
Uh, why would someone use this option?
---
Reini Urban wrote:
> add boolean option --temp-keep to pg_regress to keep the existing
> tmp_check installation, instead of overwriting it with a fresh make
> install. Useful to t
Patch applied. Thanks.
I made some small wording adjustments. Patch attached.
---
Ed L. wrote:
> The attached patch forces queryless duration log statements to be turned off
> in step with the log_statement directive.
Patch applied. Thanks.
---
David Fetter wrote:
> Folks,
>
> This patch clarifies the usage of references in PL/Perl :)
>
> Cheers,
> D
> --
> David Fetter [EMAIL PROTECTED] http://fetter.org/
> phone: +1 510 893 6100
It seems Peter has already applied many of the cleanups you suggested.
If you have more, would you download the snapshot and send in a new
patch? Thanks.
---
Euler Taveira de Oliveira wrote:
> Hi,
> This small patch correc
Patch applied. Thanks.
---
Abhijit Menon-Sen wrote:
> I have attached 5 patches (split up for ease of review) to plperl.c.
>
> 1. Two minor cleanups:
>
> - We don't need to call hv_exists+hv_fetch; we should just che
Patch applied. Thanks.
---
Magnus Hagander wrote:
> The previous build rules caused each binary to be re-linked on every
> "make", even if nothing had changed. With this patch, it's only relinked
> if it's actually updated
Reini Urban <[EMAIL PROTECTED]> writes:
> add boolean option --temp-keep to pg_regress to keep the existing
> tmp_check installation, instead of overwriting it with a fresh make
> install. Useful to test minor modifications in the current tmp_check
> installation.
This doesn't seem like a parti
Bruce Momjian schrieb:
Uh, why would someone use this option?
after fixing a minor issue, not to wait for a full
de-install / install and test database loss.
minor issues can be regression tests updates, or updated single binaries.
---
Reini Urban wrote:
> Bruce Momjian schrieb:
> > Uh, why would someone use this option?
>
> after fixing a minor issue, not to wait for a full
> de-install / install and test database loss.
>
> minor issues can be regression tests updates, or updated single binaries.
Seems to be of too limited a
Reini Urban <[EMAIL PROTECTED]> writes:
> Bruce Momjian schrieb:
>> Uh, why would someone use this option?
> after fixing a minor issue, not to wait for a full
> de-install / install and test database loss.
> minor issues can be regression tests updates, or updated single binaries.
Personally I f
Marek Lewczuk schrieb:
Reini Urban wrote:
Bruce Momjian schrieb:
Great. Thanks. I was getting conflicting reports of Cygwin problems
before.
Not for me:
I found a problem with my pg_ctl patch (WIN32 is always defined in
cygwin when windows.h is included, and the START /B postmaster cmdline
does
Patch applied. Thanks.
I simplified your test and made the error message a #define that is now
used consistently in all places. Patch attached.
---
Sean Chittenden wrote:
> pg_ctl(1)'s -w option works well if the default
Patch applied. Thanks.
I fixed a few merge conflicts.
---
Magnus Hagander wrote:
> >*** src/interfaces/libpq/fe-secure.c 28 Sep 2004 00:06:02
> >-1.54
> >--- src/interfaces/libpq/fe-secure.c 11 Oct 2004 19:50
I did things a little differently. I #undef WIN32 after including
windows.h on Cygwin and kept the defines the same except for the use of
START. This makes things more consistent.
Applied.
---
Reini Urban wrote:
> Marek L
Bruce Momjian schrieb:
I did things a little differently. I #undef WIN32 after including
windows.h on Cygwin and kept the defines the same except for the use of
START. This makes things more consistent.
But more verbose. :)
But consistency is also good.
Applied.
Thanks.
BTW, FYI: The current rema
David Helgason wrote:
On 14. okt 2004, at 21:09, Andrew Dunstan wrote:
It has just been brought to my attention that we are being very
restrictive about what we allow to be done in trusted plperl.
Basically we allow the :default and :base_math set of operations (run
perldoc Opcode or see
http:
17 matches
Mail list logo