Christopher Kings-Lynne kirjutas N, 06.02.2003 kell 03:56:
> > > set regex_flavor = advanced
> > > set regex_flavor = extended
> > > set regex_flavor = basic
> > [snip]
> > > Any suggestions about the name of the parameter?
> >
> > Actually I think 'regex_flavor' sounds fine.
>
> Not more A
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> You want regex_flavour? ;-)
> Hehe - yeah I don't really care. I have to use 'color' often enough
> accessing 100% of the world's programming APIs...
> How about regex_type, regex_mode, regex_option, etc.? ;)
Well, I used "flavor" in my p
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> >> Actually I think 'regex_flavor' sounds fine.
>
> > Not more Americanisms in our config files!! :P
>
> You want regex_flavour? ;-)
Hehe - yeah I don't really care. I have to use 'color' often enough
accessing 100% of the world's programm
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> Actually I think 'regex_flavor' sounds fine.
> Not more Americanisms in our config files!! :P
You want regex_flavour? ;-)
regards, tom lane
---(end of broadcast)---
T
> > set regex_flavor = advanced
> > set regex_flavor = extended
> > set regex_flavor = basic
> [snip]
> > Any suggestions about the name of the parameter?
>
> Actually I think 'regex_flavor' sounds fine.
Not more Americanisms in our config files!! :P
Chris
-
> Hmmm... does anyone remember the name of that NFS testing tool the
> FreeBSD guys were using? Think it came from Apple. They used it to
> find and isolate bugs in the FreeBSD code a while ago.
fsx
Chris
---(end of broadcast)---
TIP 1: subscr
On Thu, 5 Feb 2003, Greg Copeland wrote:
> > > > > Who will actually hold the key? Where will it be physically kept?
> > >
> > > Good question but can usually be addressed.
> >
> > It can be addressed, but how well? This is another big issue that I
> > don't see any plan for that I'm comfortable w
On Wed, 5 Feb 2003, Laurette Cisneros wrote:
>
> Well this isn't any good...the primary site is hugely busy and it is not on
> any of the mirrors. Perhaps it did not get copied over to the mirrors even
> though this announcent says it is there?
ftp.us.postgresql.org has had it for a day or two n
> Nice work, Tatsuo! Wade, can you confirm that this patch solves your
> problem?
>
> Tatsuo, please commit into REL7_3 branch only --- I'm nearly ready to do
> a wholesale replacement of the regex code in HEAD, so you wouldn't
> accomplish much except to create a merge problem for me ...
Ok. I h
On Wed, 2003-02-05 at 20:41, Laurette Cisneros wrote:
> I was trying from the postgresql.org download web page and following the
> mirror links there...and none of them that I was able to get to (some of
> them didn't work) showed 7.3.2.
I got it from mirror.ac.uk yesterday
--
Oliver Elphick
Thor Lancelot Simon <[EMAIL PROTECTED]> writes:
>> Unless NetBSD has changed from its heritage, the kernel disk cache
>> buffers are 8K, and so an 8K NFS read or write would never cross a
>> cache buffer boundary. But 32K would.
> I don't know what "heritage" you're referring to, but it has never
I was trying from the postgresql.org download web page and following the
mirror links there...and none of them that I was able to get to (some of
them didn't work) showed 7.3.2.
The second link you gave below works.
Thanks,
L.
On Wed, 5 Feb 2003, Tom Lane wrote:
> Laurette Cisneros <[EMAIL PRO
Laurette Cisneros <[EMAIL PROTECTED]> writes:
> Well this isn't any good...the primary site is hugely busy and it is not on
> any of the mirrors.
Sure it is. I tried two at random:
ftp://ftp.us.postgresql.org/source/v7.3.2/
ftp://ftp.dk.postgresql.org/mirrors/postgresql/source/v7.3.2/
The top-l
Well this isn't any good...the primary site is hugely busy and it is not on
any of the mirrors. Perhaps it did not get copied over to the mirrors even
though this announcent says it is there?
Thanks,
L.
On Wed, 5 Feb 2003, Marc G. Fournier wrote:
>
> G'day ...
>
> This is just a quick anno
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> On Wednesday 05 February 2003 13:04, Ian Fry wrote:
>> How about adjusting the read and write-size used by the NetBSD machine? I
>> think the default is 32k for both read and write on i386 machines now.
>> Perhaps try setting them back to 8k (it's th
On Wednesday 05 February 2003 13:04, Ian Fry wrote:
> > Wild thought here: can you reduce the MTU on the LAN linking the NFS
> > server to the NetBSD box? If so, does it help?
>
> How about adjusting the read and write-size used by the NetBSD machine? I
> think the default is 32k for both read and
Hi there,
Teodor has finished alpha version of contrib/tsearch with
ranking support. Also, it includes OpenFTS (0.34) parser, ispell and
snowball (stemming) support.
Comments and documentation are welcome !
Without documentation we'll be not able to release the module !
We need documentation with
Tom Lane wrote:
> Greg Copeland <[EMAIL PROTECTED]> writes:
> > On Wed, 2003-02-05 at 11:18, Tom Lane wrote:
> >> Wild thought here: can you reduce the MTU on the LAN linking the NFS
> >> server to the NetBSD box? If so, does it help?
>
> > I'm curious as to why you think adjusting the MTU may ha
James Hubbard wrote:
Justin Clift wrote:
Hmmm... does anyone remember the name of that NFS testing tool the
FreeBSD guys were using? Think it came from Apple. They used it to
find and isolate bugs in the FreeBSD code a while ago.
Sounds like it might be useful here.
:-)
You can find a wri
On Wed, 5 Feb 2003, Tom Lane wrote:
> 1. There are a couple of minor incompatibilities between the "advanced"
> regex syntax implemented by this package and the syntax handled by our
> old code; in particular, backslash is now a special character within
> bracket expressions. It seems to me that
Greg Copeland <[EMAIL PROTECTED]> writes:
> On Wed, 2003-02-05 at 11:18, Tom Lane wrote:
>> Wild thought here: can you reduce the MTU on the LAN linking the NFS
>> server to the NetBSD box? If so, does it help?
> I'm curious as to why you think adjusting the MTU may have an effect on
> this. Low
I have just committed the latest version of Henry Spencer's regex
package (lifted from Tcl 8.4.1) into CVS HEAD. This code is natively
able to handle wide characters efficiently, and so it avoids the
multibyte performance problems recently exhibited by Wade Klaver.
I have not done extensive perfor
Bruce,
we just released new version of contrib/btree_gist
(7.3 and current CVS) with support of int8, float4, float8
in addition to int4. Thanks Janko Richter for contribution.
Could you, please, download entire archive (12Kb) from
http://www.sai.msu.su/~megera/postgres/gist/btree_gist/btree_gist.
Justin Clift wrote:
Hmmm... does anyone remember the name of that NFS testing tool the
FreeBSD guys were using? Think it came from Apple. They used it to
find and isolate bugs in the FreeBSD code a while ago.
Sounds like it might be useful here.
:-)
You can find a write about it here:
http
On Tue, Feb 04, 2003 at 06:19:42PM -0600, Greg Copeland wrote:
>
> I do agree that a checksum (or hash) is better than nothing, however, a
> serious security solution it is not.
Which really is all I'm saying.
Kurt
---(end of broadcast)---
TIP 6
On Wed, 2003-02-05 at 11:18, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > On Wednesday 05 February 2003 11:49, Tom Lane wrote:
> >> I wonder if it is possible that, every so often,
> >> you are losing just the last few bytes of an NFS transfer?
>
> > Yah, that's kind of wha
Tom Lane wrote:
Hoo boy. I was already suspecting data corruption in the index, and
this looks like more of the same. My thoughts are definitely straying
in the direction of "the NFS server is dropping bits, somehow".
Both this and the (admittedly unproven) bt_moveright loop suggest
corrupted
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> On Wednesday 05 February 2003 11:49, Tom Lane wrote:
>> I wonder if it is possible that, every so often,
>> you are losing just the last few bytes of an NFS transfer?
> Yah, that's kind of what it looked like when I tried this before
> Christmas too
On Wednesday 05 February 2003 11:49, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > Hmm. This time it passed that point but this happened:
> >
> > COPY "certificate" FROM stdin;
> > NOTICE: copy: line 253677, bt_insertonpg[certificate_pkey]: parent page
> > unfound - fixing
On Wed, 2003-02-05 at 00:22, Curt Sampson wrote:
> On Wed, 4 Feb 2003, Greg Copeland wrote:
>
> > If three people are required to sign a package prior to release,
> > what happens when one of them is unavailable for signing (vacation,
> > hospital, etc). This is one of the reasons why having a sin
Confirmed. Looks like a 100-fold increase. Thanx guys.
Explain output can be seen here:
http://arch.wavefire.com/pgregex.txt
-Wade Klaver
At 09:59 AM 2/5/03 -0500, Tom Lane wrote:
>Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>> Ok. The original complain can be sasily solved at least for single
>>
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> Hmm. This time it passed that point but this happened:
> COPY "certificate" FROM stdin;
> NOTICE: copy: line 253677, bt_insertonpg[certificate_pkey]: parent page
> unfound - fixing branch
> ERROR: copy: line 253677, bt_fixlevel[certificate_pkey]
On Wednesday 05 February 2003 10:12, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > Well, it does appear to be working but it never finishes. Here are two
> > backtraces. One was taken while it was running and the other after a
> > kill -9. The primary key file should have
On Wed, Feb 05, 2003 at 15:22:12 +0900,
Curt Sampson <[EMAIL PROTECTED]> wrote:
> On Wed, 4 Feb 2003, Greg Copeland wrote:
>
> Hm. Splitting the key into parts is a very interesting idea, but I'd
> be interested to know how you might implement it without requiring
> everybody to be physically pr
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> Well, it does appear to be working but it never finishes. Here are two
> backtraces. One was taken while it was running and the other after a kill
> -9. The primary key file should have had 322846720 bytes based on the
> database that I was cop
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Ok. The original complain can be sasily solved at least for single
> byte encoding databases. With the small patches(against 7.3.1)
> included, I got following result.
Nice work, Tatsuo! Wade, can you confirm that this patch solves your
problem?
Tatsuo,
hi..i have questions about struct pgproc (in file proc.h) and proclock ( in
file lock.h) of the postgresql source code, does anyone know the exact
difference between pgproc and proclock structs??
thank you
-sumaira
_
Protect you
On Sunday 02 February 2003 12:26, Tom Lane wrote:
> At this point I think you need to rebuild with --enable-debug and
> --enable-cassert (if you didn't already) and then capture some
> stack traces from the stuck backend. We have to find out what the
> backend thinks it's doing.
Well, it does app
On Wed, 4 Feb 2003, Greg Copeland wrote:
> If three people are required to sign a package prior to release,
> what happens when one of them is unavailable for signing (vacation,
> hospital, etc). This is one of the reasons why having a single project
> key which the core developers sign may appear
39 matches
Mail list logo
