On Wed, 12 Nov 2008, Jonah H. Harris wrote:
In a large-scale OLTP environment, uptime is paramount, and having to
restart the database to enable PITR is a big PITA.
What I did last time I was stuck with this problem was make the
archive_command point to a script I could toggle on and off outs
a error blew was reported when peforming gmake.
hba.c: In function `parse_hba_line':
hba.c:943: error: label `hba_other_error' used but not defined
gmake[3]: *** [hba.o] Error 1
there is also not definition of "hba_other_error" in both handout of the patch
and "hba.c".
Oh, I understood you. Clearly, to surely avoid any side-effect in pg_dump,
all IMMUTABLE functions must implicitly assign search_path in develop time.
It's not obvious, so I propose to include this in CONSTRAINT ... CHECK and
CREATE INDEX documentation. :-) Or - raise NOTICE if an IMMUTABLE functio
[EMAIL PROTECTED] ("Dave Page") writes:
> On Fri, Nov 14, 2008 at 8:10 AM, Simon Riggs <[EMAIL PROTECTED]> wrote:
>>
>> On Fri, 2008-11-14 at 02:21 +, Gregory Stark wrote:
>>
>>> On the other hand what does occur to me in retrospect is that I regret
>>> that I didn't think about how I was dispa
Peter Eisentraut wrote:
> It was pointed out to me today that a zero-dimensional
> matrix is a scalar. This makes a bit of sense, if you say
> that
>
> '{{56}}' is of type int[][], 2 dimensions
> '{56}' is of type int[], 1 dimension
> '56' is of type int, 0 dimensions
>
> Notice that the number
Unicron wrote:
> a error blew was reported when peforming gmake.
>
> hba.c: In function `parse_hba_line':
> hba.c:943: error: label `hba_other_error' used but not defined
> gmake[3]: *** [hba.o] Error 1
>
> there is also not definition of "hba_other_error" in both handout of
> the patch and "hb
Simon Riggs wrote:
>>> I would also like to see the feature part of normal Postgres, rather
>>> than as a compile time option. The per-row overhead would then be
>>> optional, just as WITH OIDS is optional. This would allow many
>>> applications to take advantage of row level security, without the
Andrew Chernow <[EMAIL PROTECTED]> writes:
> I am trying to compile libpq on HP-UX 10.20 using gcc 2.95.3, cpu is a
> 400MHz PA8500. I'm using the 8.3.5 tarball.
Yeah, 10.20 is a bit old and creaky, and the system headers are shy of a
load in a few places. I currently use the attached fixes.
Gregory Stark <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Aside from the above issue, there's an already known and documented risk if
>> you omit FOR UPDATE, which is that your WHERE CURRENT OF update silently
>> becomes a no-op if someone else has already updated the targ
On Thu, Oct 23, 2008 at 08:51, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Magnus Hagander wrote:
>> This patch adds a configuration option to pg_hba.conf for "clientcert".
>> This makes it possible to have different client certificate requirements
>> on different connections. It also makes sure t
On Sat, Nov 15, 2008 at 15:20, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
> we do something like:
>
> + if (access(ROOT_CERT_FILE, R_OK))
> + {
> + ssl_loaded_verify_locations = false;
> +
> + /*
> + * If root certificate file simply not found. Do
When perl function executes first time, it is too slowly, but if
execute perl function(not function which executed first time) again it
runs in 1000 times faster. Why ? how can i optimize it ?
Configure shared_preload_libraries = '$libdir/plperl' or
local_preload_libraries = '$libdir/plugins/plperl
Oleg Serov wrote:
When perl function executes first time, it is too slowly, but if
execute perl function(not function which executed first time) again it
runs in 1000 times faster. Why ? how can i optimize it ?
Configure shared_preload_libraries = '$libdir/plperl' or
local_preload_libraries = '
On Thu, Nov 13, 2008 at 05:31, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Attached patch implements client certificate authentication.
>
> I kept this sitting in my tree without sending it in before the
> commitfest because it is entirely dependent on the
> not-yet-reviewed-and-applied patch for
Gregory Stark <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> writes:
>> Well, it's contrary to SQL spec, which says that sufficiently simple
>> cursors should be updatable even if they don't say FOR UPDATE.
>>
>> However ... the more I think about it, the more I wonder if we shouldn't
"Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> Err that really should be ereport(FATAL,
I don't think that's a particularly user-friendly design.
The behavior I'd expect to see is
1. Root cert file not there: issue existing LOG message. Maybe the user is
expecting client cert verification, and m
On Sat, Nov 15, 2008 at 17:39, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Alex Hunsaker" <[EMAIL PROTECTED]> writes:
>> Err that really should be ereport(FATAL,
>
> I don't think that's a particularly user-friendly design.
>
> The behavior I'd expect to see is
>
> 1. Root cert file not there: issue exi
Tom Lane wrote:
Andrew Chernow <[EMAIL PROTECTED]> writes:
That got rid of all warnings. Although, it still fails to compile due
to gethostbyname_r:
thread.c:141: too many arguments to function `gethostbyname_r'
Hmm, did you override the fact that --enable-thread-safety fails?
I've always a
On Sat, Nov 15, 2008 at 6:12 AM, Heikki Linnakangas
<[EMAIL PROTECTED]> wrote:
> Fujii Masao wrote:
>>
>> Attached is a patch of signal handling changes for Synch Rep.
>
> It seems that we wouldn't need to use the BackendPidGetProc function, nor
> the new AuxiliaryPidGetProc function, if we stored
Hi,
IIRC, ^M is the EOL character on windows. latest cvs failed to compile
in my mingw env because src/backend/utils/Gen_dummy_probes.sed had
that character, i had to manually remove it to continue.
Besides, http://archives.postgresql.org/pgsql-committers/2008-11/msg00175.php
added the need of ha
Tom Lane wrote:
Andrew Chernow <[EMAIL PROTECTED]> writes:
I am trying to compile libpq on HP-UX 10.20 using gcc 2.95.3, cpu is a
400MHz PA8500. I'm using the 8.3.5 tarball.
Yeah, 10.20 is a bit old and creaky, and the system headers are shy of a
load in a few places. I currently use the att
Andrew Chernow <[EMAIL PROTECTED]> writes:
> That got rid of all warnings. Although, it still fails to compile due
> to gethostbyname_r:
> thread.c:141: too many arguments to function `gethostbyname_r'
Hmm, did you override the fact that --enable-thread-safety fails?
I've always assumed that th
22 matches
Mail list logo
