On Fri, Jul 04, 2003 at 15:29:37 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> 3. What should be the set of tested values? I have it as
>buffers: first to work of 1000 900 800 700 600 500 400 300 200 100 50
>connections: first to work of 100 50 40 30 20 10
> but we could certainly argu
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 08:07:12 -0400,
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
> Otherwise, what will happen when we try to import into some non-text field
> for which '' is not a valid value?
I would expect the copy to fail as it does normally.
> Spreadsheets commonly represent missing v
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
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 fiel
On Fri, May 14, 2004 at 15:31:21 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
>
> - - DJB's multilog requires a whole mess of configuration, and is
> difficult to run unless you're root. In which case you'd be far better
> off to use syslog anyway. It is rsync friendly
I use multilog and it
On Fri, May 14, 2004 at 16:02:43 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
>
> Yes, if you're running daemontools, then multilog is hands down the way
> to go. Is it daemontools that really wants to be root? That might be
> what I'm confusing it with. Anyway, my goal was to provide a solu
On Fri, May 21, 2004 at 09:34:04 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Bruno, would you be willing to write something for docs about how to use
> multilog for postgres?
What are you looking for. Do you need to know about how to in
On Fri, May 21, 2004 at 16:59:31 -0400,
Andrew Hammond <[EMAIL PROTECTED]> wrote:
>
> I would be insterested in seeing how to set up multilog by it'self. I
> figure that once you get that far, going to daemontools should be pretty
> straighforward. It's also within the scope of Postgres' logging
On Sun, May 23, 2004 at 17:32:36 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> slower. (The datatype conversions induced inside get_next_S are likely
> to outweigh any savings from counting by ints, on most modern hardware.)
You aren't even guarenteed that integer operations are faster. On th
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 t
On Thu, Aug 25, 2005 at 16:14:04 -0400,
Bruce Momjian 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 someone want
On Thu, Aug 25, 2005 at 18:44:13 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >> We already have MD5 encryption in the server. Why would someone want
> >> CRC32?
>
> >
On Thu, Jan 05, 2006 at 11:44:24 -0800,
Josh Berkus 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 we sho
On Fri, Jan 06, 2006 at 19:11:27 +0200,
Marko Kreen <[EMAIL PROTECTED]> wrote:
> On 1/6/06, Bruce Momjian 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 nextval/currval and dis
On Sat, Apr 22, 2006 at 14:20:32 -0700,
daveg <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 22, 2006 at 01:49:25PM -0700, David Fetter wrote:
> > On Sat, Apr 22, 2006 at 01:14:42PM -0700, David Gould wrote:
> >
> > > To avoid running out of swap and triggering the oom killer we have
> > > had to redu
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 t
On Sun, Feb 20, 2005 at 09:43:11 -0500,
Bruce Momjian wrote:
>
> We regularly have people on IRC who delete data and then want to recover
> it. By having the define it makes it easier for us to help them without
> them having to add actual C code.
>
> Does that make sense?
You aren't going t
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 t
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 datab
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.
N
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 Fri, Jul 08, 2005 at 20:54:40 +0300,
Marko Kreen 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 placed i
On Fri, Jul 08, 2005 at 23:03:49 +0300,
Marko Kreen 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 to
much
24 matches
Mail list logo
