Tom Lane wrote:
> Allan Engelhardt <[EMAIL PROTECTED]> writes:
> > 1. Am I the only one who are having problems with the listerver not honouring the
>NOMAIL option?
>
> Marc said yesterday that he'd been forced to rebuild the subscriber list
> for pgsql-g
You'll want to ask on the perl groups, but briefly you get an illegal seek when your
command writes to the error file descriptor:
% perl -e '`echo hi 1>&2` or warn "Oops: $! $?";'
hi
Oops: Illegal seek 0 at -e line 1.
It's a perl feature, not a bug ;-) Try
% man perlop
for se
Phil Mayers wrote:
> Try this:
>
> hdbdev=> create table ips ( ip inet, ip_txt varchar(15) );
> hdbdev=> insert into ips (ip,ip_txt) values ('192.168.1.1','192.168.1.1');
> hdbdev=> select * from ips where ip like '192.168.1.1';
> ip | ip_txt
> +
> (0 rows)
>
> hdbdev=> select * from
Tom Lane wrote:
> >> I'm doing vacuum periodically (once a hour), but perfomance
> >> still falls down.
>
> It sounds to me like you may be running into index growth problems.
> VACUUM is presently not good about shrinking indexes.
I always enjoy Tom's comments - he is the master of understa
Lee Harr wrote:
> > (Is there any good reason for this, btw.? The major vendors [Oracle, SQL
> Server, Sybase] support having logfiles (txn, redo, archive) on separate file
> systems/devices for reliability and performance.)
> >
>
> My understanding is that you _can_ do this, by shutting down th
Is there a known problem with HASH type index in PostgreSQL 7.1.2 4PGDG on Red Hat
Linux 7.1 (2.4.2 kernel)? I can't find a lot of documentation, but this is what I
observe:
[playpen]$ dropdb test; createdb test; psql -f create_table.sql test; psql -c "COPY
clients FROM '/tmp/input.txt';" te
I could only be botherd to try a million lines, but my results from 7.1.2 are below.
Basically:
1. I find about 50% database storage overhead in this case. That's not completely
silly, considering this is structured data, but seems a little high. I don't know the
internal structures well eno
