Re: Table has 22 million records, but backup doesn't see them

Поиск
Список
Период
Сортировка
От Steve Crawford
Тема Re: Table has 22 million records, but backup doesn't see them
Дата
Msg-id 49DCDBCB.3080003@pinpointresearch.com
обсуждение исходный текст
Ответ на Re: Table has 22 million records, but backup doesn't see them  (Radcon Entec <radconentec@yahoo.com>)
Ответы Re: Table has 22 million records, but backup doesn't see them  (Radcon Entec <radconentec@yahoo.com>)
Список pgsql-general
Radcon Entec wrote:
>
>
> Here is the text that results from dumping my 22-million-row feedback
> table:
>
> ...
>
> CREATE RULE feedback_partition_active AS ON INSERT TO feedback WHERE
> (new.charge > 7000) DO INSTEAD INSERT INTO feedback_active (charge,
> elapsed_time, tag_type, stack, tag_value, heating, status) VALUES
> (new.charge, new.elapsed_time, new.tag_type, new.stack, new.tag_value,
> new.heating, new.status);
>
> ...
>
> CREATE RULE feedback_partition_archived AS ON INSERT TO feedback WHERE
> (new.charge <= 7000) DO INSTEAD INSERT INTO feedback_archived_7000
> (charge, elapsed_time, tag_type, stack, tag_value, heating, status)
> VALUES (new.charge, new.elapsed_time, new.tag_type, new.stack,
> new.tag_value, new.heating, new.status);
>

Are you certain that feedback actually contains any data or is it just
the parent table and the real data is in the child tables? What is the
output of "select count(*) from only feedback;" ?

Cheers,
Steve


В списке pgsql-general по дате отправления:

Предыдущее
От: Radcon Entec
Дата:
Сообщение: Re: Table has 22 million records, but backup doesn't see them
Следующее
От: Ivan Sergio Borgonovo
Дата:
Сообщение: Re: Are there performance advantages in storing bulky field in separate table?