On Fri, 3 Nov 2000, Christof Petig wrote:
Karel Zak wrote:
On Thu, 2 Nov 2000, Zeugswetter Andreas SB wrote:
Well I can re-write and resubmit this patch. Add it as a
compile time option
is not bad idea. Second possibility is distribute it as patch
in the contrib
On Vie 03 Nov 2000 20:37, Peter Eisentraut wrote:
Martin A. Marques writes:
checking types of arguments for accept()... configure: error: could not
determine argument types
According to the documentation for Solaris 7 it should be 'accept(int,
struct sockaddr *, socklen_t *)', which is
what version of CVS are you running? when was the last time you did
anything with it?
cvs on hub hasn't been upgraded since Sept 13th, so it isn't an upgrade
issue ... and just tested from work, and I can checkout no probs ...
On Mon, 6 Nov 2000, Michael Meskes wrote:
Here's what I get
"Martin A. Marques" [EMAIL PROTECTED] writes:
Well, mine looks like:
extern int accept(int, struct sockaddr *, Psocklen_t);
This is what I have in the configure:
extern accept ($ac_cv_func_accept_arg1, $ac_cv_func_accept_arg2,
$ac_cv_func_accept_arg3 *);
Hmm ... is it possible that his
On Lun 06 Nov 2000 12:06, Tom Lane wrote:
"Martin A. Marques" [EMAIL PROTECTED] writes:
Well, mine looks like:
extern int accept(int, struct sockaddr *, Psocklen_t);
This is what I have in the configure:
extern accept ($ac_cv_func_accept_arg1, $ac_cv_func_accept_arg2,
I'm seeing a whole bunch of miscompares in the horology test today.
Is this stuff supposed to have changed behavior?
regards, tom lane
*** ./expected/horology-no-DST-before-1970.out Fri Sep 15 15:36:24 2000
--- ./results/horology.out Mon Nov 6 13:14:35 2000
On Lun 06 Nov 2000 13:28, Tom Lane wrote:
"Martin A. Marques" [EMAIL PROTECTED] writes:
Hmm ... is it possible that his compiler distinguishes between
"extern int foo(...)" and "extern foo(...)" ? Why don't we
have the return type there, anyway?
If it's of any help, I'm on Solaris 7,
New CHECKPOINT command.
Auto removing of offline log files and creating new file
at checkpoint time.
Is this the same as a SAVEPOINT?
No. Checkpoints are to speedup after crash recovery and
to remove/archive log files. With WAL server doesn't write
any datafiles on commit, only commit
New CHECKPOINT command.
Auto removing of offline log files and creating new file
at checkpoint time.
Can you tell me how to use CHECKPOINT please?
Is this the same as a SAVEPOINT?
No. Checkpoints are to speedup after crash recovery and
to remove/archive log files. With WAL server
On Mon, 6 Nov 2000, Peter Eisentraut wrote:
So apparently we'll have to use an actual option letter for passing
runtime configuration parameters. Any suggestions? Already in use are
a A b B C d D e E f F i l L m M n N o O p P Q s S t v W x
Q is not used (or broken):
morannon:~postmaster
Thomas Lockhart [EMAIL PROTECTED] writes:
I'm seeing a whole bunch of miscompares in the horology test today.
Is this stuff supposed to have changed behavior?
Yup. RTFCVSL :)
I did, but the log didn't say anything about unfixed regression test
cases. If you're going to leave some
Peter Eisentraut [EMAIL PROTECTED] writes:
How do we control the allowed paths? Should we continue with the
environment variables? Perhaps a config option listing the allowed
directories? A system catalog?
The environment variables are a pretty sucky mechanism, IMHO;
an installation-wide
Adriaan Joubert writes:
1. Constants. The current behaviour just seems somewhat strange, and I
have no idea where to fix it.
test=# select B'1001';
?column?
--
X9
(1 row)
That's because the zpbit output function chooses to represent values that
way. Whether or not it's good
Okay, so we'll do the symlinks.
CREATE DATABASE xxx WITH LOCATION='/else/where';
will clone ('cp -r') template1 in /else/where/base/id and create a
symlink to there from $PGDATA/base/id. The '/else/where' location will
be stored in pg_database.datpath.
How do we control the allowed paths?
On Sat, Nov 04, 2000 at 10:09:16PM -0800, Vadim Mikheev wrote:
I think that to handle locations we could symlink catalogs - ln -s
path_to_database_in_some_location .../base/DatabaseOid
But that's a kludge. We ought to discourage people from messing with the
storage internals.
Hiroshi Inoue [EMAIL PROTECTED] writes:
RelationCacheInvalidate() is called from ResetSystemCaches()
and calles RelationFlushRelation() for all relation descriptors
except some nailed system relations.
I'm wondering why nailed relations could be exceptions.
Conversely why must
I need to compile a complete list of different locations to find
"libpq-fe.h" in various PostgreSQL distributions so that I can
automatically add the correct path when compiling a client application.
Please post the location "libpq-fe.h" for your distribution and I will
compile a list and
17 matches
Mail list logo
