> "BM" == Bruce Momjian <[EMAIL PROTECTED]> writes:
BM> Uh, if you supply just a number with no units, is that bytes or
BM> kilobytes? Do you have to say "0B".
If you supply 0, all units should be ignored. GUC probably doesn't do
that, but it should.
/Benny
---(en
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Personally I don't find the argument about "someday we might want
TL> to support measurements in millibits" to be convincing at all, and
TL> certainly it seems weaker than the argument that "units should be
TL> case insensitive because everyth
> "JCN" == Jim C Nasby <[EMAIL PROTECTED]> writes:
JCN> Truth is, I bet many (if not most) DBAs barely know that case
JCN> matters in the units.
Sounds like the school system needs fixing, then.
/Benny
---(end of broadcast)---
TIP 7: You ca
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Anyone against making it case-insensitive, speak now or hold your
TL> peace.
SI-units are inherently case-sensitive. The obvious example is that
now you will allow people to specify an amount in millibytes, while
interpreting it in megabytes.
> "MK" == Mark Kirkwood <[EMAIL PROTECTED]> writes:
MK> Here are the results after building gcc 4.1.2 (repeating results
MK> for gcc 3.4.6 for comparison). I suspect that performance is
MK> probably impacted because gcc 4.1.2 (and also the rest of the
MK> tool-chain) is built with gcc 3.4.6 -
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> (I suppose it wouldn't work in Windows for lack of hard links, but
TL> anyone trying to run a terabyte database on Windows deserves to
TL> lose anyway.)
Windows has hard links on NTFS, they are just rarely used.
/Benny
--
> "MW" == Mark Woodward <[EMAIL PROTECTED]> writes:
MW> Yea, I've been toying with the idea of that setting lately, I
MW> can't for the life of me understand why it isn't the default
MW> behavior.
Lots of programs handle malloc() failures very badly. Including
daemons. Often it's better in pr
> "ZA" == Zeugswetter Andreas DCP SD <[EMAIL PROTECTED]> writes:
ZA> Yes, but it obviously does not in some ports, and that was the
ZA> main problem as I interpreted it.
strncpy is part of POSIX; I highly doubt anyone gets it wrong. Getting
sane semantics from it does require manually writing
> "CN" == Csaba Nagy <[EMAIL PROTECTED]> writes:
CN> The full story is that I typed 'ΓΌ' (u-umlaut if it won't render
CN> correctly) and backspace before the '1'. I guess the backspace
CN> will delete byte-wise and will so fail to delete properly
CN> multi-byte characters.
Backspace deletes ch
> "MvO" == Martijn van Oosterhout writes:
MvO> What we want is just a monotonically increasing counter that can
MvO> be read quickly and consistantly, we're not majorly fussed if it
MvO> doesn't match real time. This puts us back to CPU cycle counters,
MvO> but they have drawbacks of their ow
> "MvO" == Martijn van Oosterhout writes:
MvO> Is this of practical use for run-of-the-mill video cards? --
The article suggests that using the GPU is a win even on a $100 64MB
card. The built-in card in most servers is probably not worth
bothering with, but many servers offer PCI Express th
11 matches
Mail list logo
