I'm puzzled with the date formats in
the 7.0b2 version. Perhaps I'm missing something
trivial, (SQL standards?) but I have been using postgres
from years, and never had this kind of problem.
I use the -e switch, so that
> dates passed to and from the
> frontend processes will be
> assumed to be i
--- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > What's the advantage of using pg_dumpall over
> tar/gzip for backup?
>
> pg_dumpall grabs a constent snapshot of the data.
> tar/gzip is just
> backing up the files, so you can get some data in
> some table that is
> committed, but miss data in an
-- Brian Baquiran <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm using Postgres 6.5.2 in a high-volume
> application that has on the order of a
> hundred inserts and selects (but mostly inserts) a
> minute. My loadaverage hovers
> around 1.0, and can go much, much higher (50-80)
> during vacuum and que
My table 'clientes' has a serial field,
with name 'rid'.
Now, take a look at these queries:
ss => select rid from clientes where rid > 18974 and
rid < 18976;
rid
-
18975
(1 row)
ss => select rid from clientes where rid = 18975;
rid
---
(0 rows)
A vacuum (or vacuum analyze) did
My init script includes this line
(in red hat 6.1):
echo "1" > /proc/sys/kernel/shmmax
to increase the available shared memory,
and afterwards:
/sql/bin/postmaster -B5892 -D/sql/data -o "-e -B5892
-S4000 -F" -i >> /sql/log/sql.log
> When fsync is off, how is
> data loss possible?
>
