Posted about 2 weeks to the "General" and "Questions" lists. Got no answers
and found no workaround (yet !).
Any ideas ?
Emmanuel Charpentier
PS : If possible, Please Cc: to [EMAIL PROTECTED] : I'm reading
the list through the news server, and nor very often ...
Original Message
On Mon, 2003-02-03 at 22:35, Curt Sampson wrote:
> 2. Do I trust him to take care of his own key and be careful signing
> other keys?
>
> 3. Do I trust his opinion that the postgres release-signing key that
> he signed is indeed valid?
>
> 4. Do I trust the holder of the postg
On Tue, 3 Feb 2003, Greg Copeland wrote:
> Surely there are a couple of key developers whom would be willing to
> sign each other's keys and have previously met before. Surely this
> would be the basis for phone validation. Then, of course, there is 'ol
> snail-mail route too. Of course, nothin
On Mon, 2003-02-03 at 22:35, Curt Sampson wrote:
> On Mon, 3 Feb 2003, Kurt Roeckx wrote:
>
> > I'm not saying md5 is as secure as pgp, not at all, but you can't
> > trust those pgp keys to be the real one either.
>
> Sure you can. Just verify that they've been signed by someone you trust.
>
> F
On Monday, February 3, 2003, at 04:39 AM, Bruce Momjian wrote:
I looked at that URL, and it is good example of what _not_ to do with
interactive docs, IMHO. The manual page is _very_ short, and shows no
examples. The comments have various examples/cases, with corrections
later to earlier postin
On Mon, 2003-02-03 at 13:55, Kurt Roeckx wrote:
> On Mon, Feb 03, 2003 at 12:24:14PM -0600, Greg Copeland wrote:
> > On Sun, 2003-02-02 at 20:23, Marc G. Fournier wrote:
> >
> > > right, that is why we started to provide md5 checksums ...
> >
> > md5 checksums only validate that the intended pack
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> Would you poke into it and see why?
> I can, but I'm not sure what you want me to do -
It shouldn't be that hard to find why you're getting zeroes instead of
expected results. I'd look at those cases first.
regards
On Mon, 3 Feb 2003, Kurt Roeckx wrote:
> I'm not saying md5 is as secure as pgp, not at all, but you can't
> trust those pgp keys to be the real one either.
Sure you can. Just verify that they've been signed by someone you trust.
For example, next time I happen to run into Bruce Momjian, I hope
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Latest CVS, timetz and horology is failing...
Would you poke into it and see why?
I made some recent adjustments to the rounding code in timetz, but I
didn't expect any portability issues to surface...
regards, tom l
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > Latest CVS, timetz and horology is failing...
>
> Would you poke into it and see why?
I can, but I'm not sure what you want me to do - I'm not really familiar
with it all bar the stuff I attached to the email...
Chris
-
Next question: may I guess that you weren't using MULTIBYTE in 7.2?
After still more digging, I'm coming round to the opinion that the
problem is that MULTIBYTE is forced on in 7.3, and this imposes a
factor-of-256 overhead in a bunch of the operations in regcomp.c.
In particular, compiling a case
Wade, how many distinct patterns do you have in that table? What's the
population distribution (in particular, do the top 32 patterns account
for most of the table)?
It's looking like the issue is not so much that the 7.3 code is
completely broken, as that its LRU replacement policy for precompil
Latest CVS, timetz and horology is failing...
parallel group (13 tests): text name varchar float4 char int2 boolean oid
int8 float8 bit int4 numeric
boolean ... ok
char ... ok
name ... ok
varchar ... ok
text
Bruce Momjian wrote:
(B>
(B> It also clarifies the docs to mention it sits on the last row, not after
(B> the last row.
(B
(BIs it true ?
(B
(Bregards,
(BHiroshi Inoue
(Bhttp://www.geocities.jp/inocchichichi/psqlodbc/
(B
(B---(end of broadcast)--
Well, IMHO I would rather see a delay of the roll-out by a day or two
than see a release with such a serious performance glitch. Especially
since I personally have been shooting my big mouth off to all my geek
friends on the leaps and bounds PG has made in the last few releases. With
my luck on
Sigh. It seems that somebody broke caching of compiled regexes,
so that your regex is recompiled each time it's used. I haven't
dug into the logic yet, but I think it must have been a mistake
in Thomas' change to make the regex cache be searched circularly:
2002-06-14 22:49 thomas
* sr
At 05:51 PM 2/3/03 -0500, Tom Lane wrote:
>wade <[EMAIL PROTECTED]> writes:
>> Here is the profile information. I included a log of the session that
>> generated it at the top of the gprof output. If there is any other info I
>> can help you with, please let me know.
>
>A four-second test isn't
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 03, 2003 3:31 PM
> To: Dann Corbit; Merlin Moncure
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Win32 and fsync()
>
>
> I'm not sure what the provenance of this code for _commit is
> - I
I'm not sure what the provenance of this code for _commit is - I thought it
was in the standard MS libs - have they finally seen the light and open
sourced it? ;-)
andrew
- Original Message -
From: "Dann Corbit" <[EMAIL PROTECTED]>
To: "Merlin Moncure" <[EMAIL PROTECTED]>; "Andrew Dunstan
On Mon, 3 Feb 2003, Dann Corbit wrote:
> > -Original Message-
> > From: Merlin Moncure [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, February 03, 2003 3:00 PM
> > To: Andrew Dunstan
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [HACKERS] Win32 and fsync()
> >
> >
> > >I'm having difficulty
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 03, 2003 3:00 PM
> To: Andrew Dunstan
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Win32 and fsync()
>
>
> >I'm having difficulty digging up the reference, but I think I recall
> seeing >s
On Mon, 3 Feb 2003, Andrew Dunstan wrote:
> I'm also fairly sure I saw something like
> #define fsync _commit
> in the Berkeley DB sources the other day, which might be a clue.
>
> I'll be happy to be corrected, though.
You'd be right:
/*
* Win32 has fsync, getcwd, snprintf and vsnprintf,
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 22:47
> To: PostgreSQL Hackers
> Subject: Re: [HACKERS] Win32 and fsync()
>
>
> I'm having difficulty digging up the reference, but I think I
> recall seeing something that said, roughly, o
>I'm having difficulty digging up the reference, but I think I recall
seeing >something that said, roughly, on W32 there are 2 sets of buffers
- those in >the user level library and those in the kernel level driver,
and >FlushFileBuffers drains the first, while _commit drains both (it
includes a >c
wade <[EMAIL PROTECTED]> writes:
> Here is the profile information. I included a log of the session that
> generated it at the top of the gprof output. If there is any other info I
> can help you with, please let me know.
A four-second test isn't long enough to gather any statistically
meaningf
I'm having difficulty digging up the reference, but I think I recall seeing
something that said, roughly, on W32 there are 2 sets of buffers - those in
the user level library and those in the kernel level driver, and
FlushFileBuffers drains the first, while _commit drains both (it includes a
call t
>> For Win32, in order to emulate fsync() we will need to call
>> FlushFileBuffers():
The supplied link does not work. FlushFileBuffers() is for flushing
files opened with CreateFile() etc.
For files opened with fopen(), call fflush().
For files opened with _open(), call _commit().
Likekly the
At 10:52 PM 1/31/03 -0500, Tom Lane wrote:
>wade <[EMAIL PROTECTED]> writes:
>> We recently upgraded a project from 7.2 to 7.3.1 to make use of some of
>> the cool new features in 7.3. The installed version is CVS stable from
>> yesterday. However, we noticed a major performance hit in POSIX re
> -Original Message-
> From: Hannu Krosing [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 22:30
> To: Dave Page
> Cc: PostgreSQL Hackers; Katie Ward
> Subject: Re: [HACKERS] Win32 Powerfail testing - results
>
>
> Your hardware should also be able to run Postgres on BeOS
>
> http
Dave Page kirjutas E, 03.02.2003 kell 18:51:
> Well the results are finally in. Hopefully we can concentrate on putting
> them right, rather than having a round of "told you so's" :-)
>
> I modified the test program slightly to improve the consistency checks.
> The updated version is attached.
>
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 21:52
> To: Dave Page
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Win32 Powerfail testing - results
>
>
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > Rod Taylor allegedly
Merlin Moncure wrote:
>
> Just a quick question... are you guys using the C runtime or the win32
> API to do things like file i/o and memory allocation. If you are using
> the win32 api, are you using asynchronous I/O? Generally, how much raw
> win32 code do you expect to write (assumption: as l
Lamar Owen wrote:
>
> On Friday 31 January 2003 03:21, Bruce Momjian wrote:
> > Man, I go away for one day, and look what you guys get into. :-)
>
> No duh. Whew.
>
> > Lastly, SRA just released _today_ their first Win32 port of PostgreSQL,
> > and it is _threaded_:
>
> > http://osb.sra
"Dave Page" <[EMAIL PROTECTED]> writes:
> Rod Taylor allegedly said:
>> Any change of tossing in a periodic VACUUM or would that throw off the
>> results?
> Dunno, Tom could best answer that, but a *complete guess* based on piecing
> together tidbits of how it all works from various threads here,
[EMAIL PROTECTED] wrote:
What might be "nifty" would be to have some mappings that did Clever
Transformations of Queries Into Views, particularly if that allowed
harnessing the DBMS to do some of the statistical analysis behind your
back...
I'm not quite sure what you mean here, but it does supp
Hannu Krosing wrote:
>
> On Thu, 2003-01-30 at 20:29, Tom Lane wrote:
> > Claiming that it doesn't require an increased level of testing is
> > somewhere between ridiculous and irresponsible.
>
> We should have at least _some_ platforms (besides Win32) that we could
> clain to have run thorough t
> >>Any strong feelings on whether this is necessary for a first release?
> >
> > No. I'm not sure you'd really need triggers written in R ever ;-)
>
> Yeah, that's what I figured too.
Indeed. R sounds like it might be an interesting platform from which to
do "data mining," and in that sort of
For Win32, in order to emulate fsync() we will need to call
FlushFileBuffers():
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/
base/flushfilebuffers.asp
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go t
oh joy, here we go again ...
you are right, my mistake :( I copied out of peter's directory ... fixing
now ...
On Mon, 3 Feb 2003, Lamar Owen wrote:
> On Monday 03 February 2003 11:38, Marc G. Fournier wrote:
> > Will announce tomorrow morning if there are no issues with it ...
>
> Where did
On Mon, Feb 03, 2003 at 12:24:14PM -0600, Greg Copeland wrote:
> On Sun, 2003-02-02 at 20:23, Marc G. Fournier wrote:
>
> > right, that is why we started to provide md5 checksums ...
>
> md5 checksums only validate that the intended package (trojaned or
> legit) has been properly received. They
On Monday 03 February 2003 11:38, Marc G. Fournier wrote:
> Will announce tomorrow morning if there are no issues with it ...
Where did the following three man pages go?
man1/clusterdb.1
man1/pg_controldata.1
man1/pg_resetxlog.1
In 7.3.1 they were at:
./postgresql-7.3.1/doc/man1/clusterdb.1
./pos
Tom Lane wrote:
Joe Conway <[EMAIL PROTECTED]> writes:
2) Knowing the trend to move stuff *out* of the PostgreSQL source tarball, and
assuming plr is released under GPL, is there any chance that it would be
accepted into src/pl or contrib, or should I start a gborg project (I'd prefer
if it co
Rod Taylor allegedly said:
>> I modified the test program slightly to improve the consistency
>> checks. The updated version is attached.
>
> For curiosity sake, I've compiled it and am running it on FreeBSD with
> soft-updates enabled.
>
> A few variable declarations needed to be bumped up to the
Vince Vielhaber allegedly said:
> On Mon, 3 Feb 2003, Dave Page wrote:
>
>> Run | Errors Detected
>> =
>> 07 | COUNT CHECK - Duplicate or missing rows detected (10262)!! 09 |
>> DISTINCT CHECK - Duplicate or missing rows detected (9893)
> I modified the test program slightly to improve the consistency checks.
> The updated version is attached.
For curiosity sake, I've compiled it and am running it on FreeBSD with
soft-updates enabled.
A few variable declarations needed to be bumped up to the top of their
respective function.
An
On Sun, 2003-02-02 at 20:23, Marc G. Fournier wrote:
> right, that is why we started to provide md5 checksums ...
md5 checksums only validate that the intended package (trojaned or
legit) has been properly received. They offer nothing from a security
perspective unless the checksums have been si
The only MFC dependency is CWinApp, which I agree can be replaced. The rest
of it is written in c++ -- no MFC dependencies. C++ is still important
because of the critical-scection locking/unlocking through automatic stack
variables.
Katie
> -Original Message-
> From: Merlin Moncure [mai
At 08:31 PM 2/1/03 +0800, Christopher Kings-Lynne wrote:
>Why on earth are you using a CVS version!?!?!?!
>
>Chris
>
This problem manifests itself under 7.3.1 release as well. CVS is used so
we can access patches to the SRF stuff implemented after 7.3.1 was released.
Tom... any links that documen
On Mon, 3 Feb 2003, Dave Page wrote:
> Well the results are finally in. Hopefully we can concentrate on putting
> them right, rather than having a round of "told you so's" :-)
>
> I modified the test program slightly to improve the consistency checks.
> The updated version is attached.
[...]
>
>
> (3) Sign official releases using the PGDG private key, and provide the
> signatures on www.postgresql.org along with the packages themselves.
Sounds about right. I'd go as far as to sign release announcements and
security emails as well.
--
Rod Taylor <[EMAIL PROTECTED]>
PGP Key: http://www.r
Well the results are finally in. Hopefully we can concentrate on putting
them right, rather than having a round of "told you so's" :-)
I modified the test program slightly to improve the consistency checks.
The updated version is attached.
Regards, Dave.
System
==
Gigabyte GA-6VTXD Motherbo
On Sun, 2003-02-02 at 21:23, Marc G. Fournier wrote:
> well, if you want to tell me the steps, I'll consider it ...
I certainly wouldn't consider myself to be an expert in PGP, but my
understanding of the basic steps is:
(1) Generate a public/private key pair for the PGDG team. This should be
use
>Can the ConsoleApp thing be written in C so we don't have to get an
>extra C++ compiler for one file (for those who don't want to use the
>Microsoft toolchain)?
Critical sections and semaphores and mutexes are all available from the
win32 API. I agree with Peter: I am not sure it is a good idea
Will announce tomorrow morning if there are no issues with it ...
%ls -lt ~ftp/pub/source/v7.3.2
total 21677
-rw-r--r-- 1 pgsql pgsql70 Feb 3 11:36 postgresql-test-7.3.2.tar.gz.md5
-rw-r--r-- 1 pgsql pgsql65 Feb 3 11:36 postgresql-7.3.2.tar.gz.md5
-rw-r--r-- 1 pgsql pgsql
Peter Eisentraut wrote:
> I have prepared a little patch that makes room for a native Windows build
> in our existing build framework. The Cygwin port would be renamed to
> "cygwin" and the new port takes over the "win" name. I have prepared the
> port specific template and makefile and extracted
> -Original Message-
> From: Rod Taylor [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 13:18
> To: Dave Page
> Cc: Bruce Momjian; Neil Conway; PostgreSQL Hackers
> Subject: Re: [HACKERS] Interactive Documentation - how do you
> want ittowork?
>
>
> > The only effort required woul
I'm nearing completion of a new procedural language, PL/R. It provides an
interface to the R Statistical Computing language. R is similar to the
commercial package S-Plus; for more on R see:
http://www.r-project.org/
Here is the first paragraph of their intro:
"R is a language and environment
OK, NO ACTION (the default) no longer prints for foreign key constraints:
regression=> \d clstr_tst
Table "public.clstr_tst"
Column | Type |Modifiers
+-+-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I think we should PGP sign all the "official" packages that are
> provided for download from the various mirror sites.
Doesn't anyone around here read pgsql-general? :) I've been arguing for
this over there since June of last year. I've also bee
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 14:39
> To: Dave Page
> Cc: Bruce Momjian; Neil Conway; PostgreSQL Hackers
> Subject: Re: [HACKERS] Interactive Documentation - how do you
> want it towork?
>
>
> "Dave Page" <[EMAIL PROTECTED]>
"Dave Page" <[EMAIL PROTECTED]> writes:
> Perhaps we should then prune the garbage out of the old version, and
> make the comments version specific so that we start afresh with the new
> docs, but leave the useful comments against the older versions?
It seems clear to me that the comments *should*
The following patch removes FETCH LAST and instead supports FETCH ALL.
It also clarifies the docs to mention it sits on the last row, not after
the last row.
Applied.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]>
> The only effort required would be to note and delete the 'junk' comments
> which is minimal work, especially if going through them anyway. There is
> no web interface for deletion (yet) but it will identify the comment IDs
> for you. I'm happy to accept lists of items to delete.
Toss an 'Send no
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 13:04
> To: Dave Page
> Cc: Neil Conway; PostgreSQL Hackers
> Subject: Re: [HACKERS] Interactive Documentation - how do you
> want it towork?
>
> > Perhaps we should then prune the garbage ou
Dave Page wrote:
>
> > -Original Message-
> > From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> > Sent: 03 February 2003 11:40
> > To: Dave Page
> > Cc: Neil Conway; PostgreSQL Hackers
> > Subject: Re: [HACKERS] Interactive Documentation - how do you
> > want it towork?
> >
> >
> >
> >
Dave Page wrote:
> > I looked at that URL, and it is good example of what _not_ to
> > do with interactive docs, IMHO. The manual page is _very_
> > short, and shows no examples. The comments have various
> > examples/cases, with corrections later to earlier postings.
> > I would think this
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.
---
Ross J. Reedstrom wrote:
> On Fri, Jan 10
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.
---
Lee Kindness wrote:
Content-Description:
> All of these lock functions succeed when the same process asks for a
> lock that it already has. That is:
>
> fcntl(fd, ...);
> fcntl(fd, ...); /* success -- no error returned */
>
> For flock() only, the lock is inherited by a child process along
> with the file descriptor so the ch
Bruce Momjian wrote:
> I looked at that URL, and it is good example of what _not_ to do with
> interactive docs, IMHO. The manual page is _very_ short, and shows no
> examples. The comments have various examples/cases, with corrections
> later to earlier postings. I would think this is not what
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 11:40
> To: Dave Page
> Cc: Neil Conway; PostgreSQL Hackers
> Subject: Re: [HACKERS] Interactive Documentation - how do you
> want it towork?
>
>
>
> I looked at that URL, and it is good exa
I must remember not to wake up this early again. I must have been reading the wrong
manpage.
Thanks :)
-*- Bruce Momjian <[EMAIL PROTECTED]> [ 2003-02-03 11:41 ]:
>
> Uh, it is configurable. See psql manual page.
>
> ---
Uh, it is configurable. See psql manual page.
---
Þórhallur Hálfdánarson wrote:
> Hi
>
> mydatabase=#
>
> What about making this configurable, so that one could for examble change is prompt
>to:
>
> me:mydatabase@myhost
I looked at that URL, and it is good example of what _not_ to do with
interactive docs, IMHO. The manual page is _very_ short, and shows no
examples. The comments have various examples/cases, with corrections
later to earlier postings. I would think this is not what we want. We
want a longer m
- Original Message -
From: "Justin Clift" <[EMAIL PROTECTED]>
To: "Curt Sampson" <[EMAIL PROTECTED]>
Cc: "Peter Eisentraut" <[EMAIL PROTECTED]>; "Curtis Faith"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, February 02, 2003 4:42 AM
Subject: Re: [mail] Re: [HACKERS] Windows Build S
> That same documentation mentions that locks acquired using flock()
> will *not* invoke the mandatory lock semantics even if on a file
> marked for it, so I guess flock() isn't implemented on top of fcntl()
> in Linux.
They're not. And there's another difference between fcntl and flock in
Linux:
Hi
mydatabase=#
What about making this configurable, so that one could for examble change is prompt to:
me:mydatabase@myhost=#
Would a patch be accepted if I ever would get around to it? (I won't have time for the
next few weeks, so if anyone else wants to do the implementation: feel free :)
Hi Bruce,
Have you ever used the idocs on the PHP site? I find them invaluable,
though there are many useful comments that you might not want to
incorporate into the official docs for fear of bloating them. Take a
look at http://www.php.net/manual/en/function.intval.php for example.
Regards, Dave
Tom Lane wrote:
> On HPUX 10.20, flock doesn't seem to exist (hasn't got a man page nor
> any mention in /usr/include).
Correct. Still isn't there in later releases.
> lockf says
>
> All locks for a process are released upon
> the first close of the file, even if the process still
79 matches
Mail list logo
