> But is it really important? All Unixen that I know of handle process
> text segments on a page-by-page basis; pages that aren't actually being
> touched won't get swapped in. Thus, the unused maps will just sit on
> disk, whether they are part of the main executable or a separate file.
> I dou
fixing
On Fri, 17 Aug 2001, D'Arcy J.M. Cain wrote:
> I seem to have lost my CVS access to the repository. I don't know if
> my password changed for some reason or what. I sent email to Marc but
> no response. Can someone else check my account and let me know what
> happened please. I have
I seem to have lost my CVS access to the repository. I don't know if
my password changed for some reason or what. I sent email to Marc but
no response. Can someone else check my account and let me know what
happened please. I have some PostgreSQL changes to make (including
a fix to a very nast
Once the mirrors come up to speed, you may download the latest RPMset from:
/pub/binary/v7.1.3/RPMS
Please actually read the file 'README.rpm-dist' in that directory BEFORE
installation.
Binaries are, as before, provided for Red Hat 7.1 only at this time. Source
RPM is provided, and should re
Peter Eisentraut wrote:
>
> I have so far implemented the following:
>
> An operator class text_binary_ops that does memcmp()-based comparison of
> text data. The operators are named $<$ etc. for lack of a better idea.
> That lack is further illustrated by the idea to name them "binary-<" etc.,
Bruce Momjian writes:
> > Bruce Momjian writes:
> >
> > > Anyway, the patch is small so I will apply it. There is no telling what
> > > OS's expect a character string there.
> >
> > There's a pretty good telling: Nobody ever reported a problem related to
> > this.
>
> We have had crypts that di
> Bruce Momjian writes:
>
> > Anyway, the patch is small so I will apply it. There is no telling what
> > OS's expect a character string there.
>
> There's a pretty good telling: Nobody ever reported a problem related to
> this.
We have had crypts that didn't work across platforms.
--
Bru
Can I ask why we are mentioning the changelog for the release and not
the list from the HISTORY file? Any why are we putting the changelog in
the tarball anyway? Seems that could easily go on a web site.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED]
Bruce Momjian writes:
> Anyway, the patch is small so I will apply it. There is no telling what
> OS's expect a character string there.
There's a pretty good telling: Nobody ever reported a problem related to
this.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
1. Just noted this in contrib/userlock/README.user_locks:
> User locks, by Massimo Dal Zotto <[EMAIL PROTECTED]>
> Copyright (C) 1999, Massimo Dal Zotto <[EMAIL PROTECTED]>
>
> This software is distributed under the GNU General Public License
> either version 2, or (at your option) any later ver
I have so far implemented the following:
An operator class text_binary_ops that does memcmp()-based comparison of
text data. The operators are named $<$ etc. for lack of a better idea.
That lack is further illustrated by the idea to name them "binary-<" etc.,
which wouldn't get through the parse
Tatsuo Ishii writes:
> I use Makefile.shlib to create each shared object. This way is, I
> think, handy and portble. However, I need to make lots of subdirs for
> each encoding conversion function. Any suggestions?
Given Tom Lane's comment, I think that this would be a wasted effort.
Shared obje
> Tom Lane writes:
>
> > Option 2 improves Oracle compatibility, at the price of breaking
> > backwards compatibility for applications that presently use $ as part
> > of multi-character operator names. (But does anyone know of any?)
>
> Hmm, postgresql-7.2devel_petere_privatebranch... :-(
>
>
Morning all ...
PostgreSQL v7.1.3 has just been bundled and uploaded onto the
central FTP server, with mirrors to follow over the next several hours ...
The ChangeLog file is/will be viewable on the mirrors under:
/pub/latest/README.ChangeLog
Being a p
Peter Moscatt <[EMAIL PROTECTED]> wrote in message
news:<4x9f7.126086$[EMAIL PROTECTED]>...
> I am pretty new to PostgreSQL so please bare with me :-)
>
> When issuing the CREATEDB MyDb then creating some tables with CREATE
> TABLE, I then go back and do a search for the file I have just crea
As usual i didn't cc the list :)
Magnus
- Original Message -
From: "Magnus Naeslund(f)" <[EMAIL PROTECTED]>
To: "Tom Lane" <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 6:55 PM
Subject: Re: [PATCHES] Re: [HACKERS] Re: WIN32 errno patch
> From: "Tom Lane" <[EMAIL PROTECTED]>
> [sni
"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> Tom, would it make sense to use this new type in the system tables where
> pg_class oids currently are used, such as pg_attribute.attrelid ?
Probably. We already use regproc where pg_proc OIDs are used --- not
completely consistently IIRC, but i
On Thu, Aug 16, 2001 at 10:36:49PM -0400, Tom Lane wrote:
> I said:
> > Suppose that we invent a new datatype "regclass", similar to regproc:
> > it's actually an OID, but it has the additional implication that it is
> > the OID of a pg_class row, and the I/O operations for the type try to
> > acc
Tom Lane writes:
> Option 2 improves Oracle compatibility, at the price of breaking
> backwards compatibility for applications that presently use $ as part
> of multi-character operator names. (But does anyone know of any?)
Hmm, postgresql-7.2devel_petere_privatebranch... :-(
Well, the Euro is
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Sure, if you want to remove it from operators, that is fine, but adding
> > it to identifiers seems weird seeing as only one person wants it and it
> > isn't standard.
>
> ?? I don't see any value in not using $ for *either* purpose. That
> breaks
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Sure, if you want to remove it from operators, that is fine, but adding
> it to identifiers seems weird seeing as only one person wants it and it
> isn't standard.
?? I don't see any value in not using $ for *either* purpose. That
breaks backwards com
> In fact, with $-as-identifier we'd have this useful property: given a
> lexically-recognizable identifier, substitution of a parameter token
> for the identifier does not require insertion of any whitespace to
> keep the parameter lexically recognizable. Some of you will recall
> plpgsql bugs a
I've been thinking some more about this dollar-sign business. There
are a couple of points that haven't been made yet. If you'll allow
me to recap:
It seems like there are two reasonable paths we could take:
1. Keep $ as an operator character. If we go this way, I think we
should allow a sing
23 matches
Mail list logo
