Peter Landis <[EMAIL PROTECTED]> writes:
> but when restoring the database on the new server
> using the following command
> cat dbname.pgdump | psql dbname
> It generates the some of the tables and then somewhere
> in the middle of the process of restoreing the db I
> get the following error mes
I'm currently backing up my db to be transfered from
one server to another. I backed up the db using the
% pg_dump dbname > dbname.pgdump
but when restoring the database on the new server
using the following command
cat dbname.pgdump | psql dbname
It generates the some of the tables and then so
> I'm just digging a little bit in PostgreSQL internals and I found the
> following thing. Shouldn't the reltuples field in pg_class contain the
> real number of tuples? It is always a little bit to low ...
>
> irc=# SELECT reltuples FROM pg_class WHERE relname = 'events';
> reltuples
> ---
I'm just digging a little bit in PostgreSQL internals and I found the
following thing. Shouldn't the reltuples field in pg_class contain the
real number of tuples? It is always a little bit to low ...
irc=# SELECT reltuples FROM pg_class WHERE relname = 'events';
reltuples
---
18
in continue to my previous message.
version: postgres 6.5.3-1
Problem was fixed:
1. all indexes of bugged table was dropped
2. all records from bugged table was selected into temp
table
3. bugged table was dropped
4. temp table was renamed to right name
5. neccessary indexes was created
-
Hi.
i have some table (in work ~ 5000 records)
{
mo varchar(6)
se varchar(128)
lo varchar(128)
su float8
nd int4
as float8
sk float8
}
delete from it. -> 0 records.
vacuum it -> OK
then run a program (c,libpq):
{
begin work
delete from table where ...
loop { insert ... }
