On Sun, Nov 05, 2006 at 11:49:36 -0500,
Tom Lane [EMAIL PROTECTED] wrote:
As already discussed upthread, anyone who wants the path can get it from
`pwd` or local equivalent --- and that mechanism is robust (as long as
the directory move doesn't happen while any particular instance of the
On Mon, Aug 28, 2006 at 19:35:11 +0200,
Zoltan Boszormenyi [EMAIL PROTECTED] wrote:
(BTW, is there anyone as high-ranking as them,
or the committee is a duumvirate? :-) )
There is a group referred to as core that is the final arbitrator of things.
Tom and Bruce are both members of this
On Fri, Jan 06, 2006 at 19:11:27 +0200,
Marko Kreen [EMAIL PROTECTED] wrote:
On 1/6/06, Bruce Momjian pgman@candle.pha.pa.us wrote:
Considering there's no currval() without nextval(), what point
is disallowing currval() when user is able to call nextval()?
I rather want to allow
On Thu, Jan 05, 2006 at 11:44:24 -0800,
Josh Berkus josh@agliodbs.com wrote:
Bruce, Tom,
The permissions for a sequence aren't the same as they are for a
table. We've sort of ignored the point to date, but if we're going to
add special syntax for granting on a sequence, I don't think
On Thu, Aug 25, 2005 at 16:14:04 -0400,
Bruce Momjian pgman@candle.pha.pa.us wrote:
Ilia Kantor wrote:
Both backend and users may have a nice use of the function.
Nice and fast hashing when one doesn't need encryption.
We already have MD5 encryption in the server. Why would
On Thu, Aug 25, 2005 at 18:44:13 -0400,
Tom Lane [EMAIL PROTECTED] wrote:
Bruno Wolff III [EMAIL PROTECTED] writes:
Bruce Momjian pgman@candle.pha.pa.us wrote:
We already have MD5 encryption in the server. Why would someone want
CRC32?
Lower CPU utiliization.
Like Bruce, I don't
On Fri, Jul 08, 2005 at 20:54:40 +0300,
Marko Kreen marko@l-t.ee wrote:
The idea is to initially seed Fortuna with randomness from
system and later feed SHA1 of user data into it too. Just
to keep it from degenerating into pure PRNG.
How is fortuna getting entropy?
Wouldn't this be better
On Fri, Jul 08, 2005 at 23:03:49 +0300,
Marko Kreen marko@l-t.ee wrote:
Well, those OS'es that already have urandom/random, don't need
it. And those that don't - I really don't feel responsibility
to write one...
But fortuna is essentially a high quality /dev/urandom. It doesn't make seem
On Tue, Jun 21, 2005 at 08:42:16 +0300,
Eugen Nedelcu [EMAIL PROTECTED] wrote:
One solution to deal with this is to use to_char function, but for
complex selects against multiple tables it's not a good option.
Why not? You only have to apply it to the output expressions that
need it.
Note
On Tue, Jun 21, 2005 at 16:03:43 +0300,
Eugen Nedelcu [EMAIL PROTECTED] wrote:
This is a patch for psql client and not for the backend. It's role
is to output numbers to screen in easy readable form (2,345,675,454,543
is much easier to read then 2345675454543.456). I think graphical
On Sat, Jun 18, 2005 at 09:27:49 -0400,
Robert Treat [EMAIL PROTECTED] wrote:
On Saturday 18 June 2005 04:55, Andreas Pflug wrote:
Magnus Hagander wrote:
Umm. Tiny item, but your comment still refers to the database as
pg_system ;-)
What is the purpose of this database? A
On Fri, Jun 03, 2005 at 09:43:13 -0700,
Mary Edie Meredith [EMAIL PROTECTED] wrote:
Looking at this from another angle, is there really any way that you can
say a write is truly guaranteed in the event of a failure? I think in
the end to be safe, you cannot. That's why (and I'm not
On Tue, Apr 13, 2004 at 06:58:24 -0400,
Andrew Dunstan [EMAIL PROTECTED] wrote:
One area that we should think about as an enhancement is NOT NULL fields.
As it stands now, we will get what we normally get when we try to insert
a null into a NOT NULL field, namely an error. If the field has
On Mon, Apr 12, 2004 at 02:26:14 -0400,
Andrew Dunstan [EMAIL PROTECTED] wrote:
a few points:
. in CSV mode, NULL should default to '' - that was in what I sent in.
Postgres normally treats an empty string as an empty string. Are you sure
you really want it to be treated as a NULL by
On Mon, Apr 12, 2004 at 10:30:22 -0400,
Bruce Momjian [EMAIL PROTECTED] wrote:
It is my understanding that \N is a valid column value (no backslash
escape in CSV, right?), so we can't use it for NULL.
The only thing I can think of is for NULL to be:
,,
(no quotes) and a
15 matches
Mail list logo
