We have a database that we're upgrading from 8.2 to 8.3. Our basic
prodecure is to make a backup of the data using pgAdmin, remove 8.2,
install 8.3, then use pgAdmin to restore the data. That works fine on
our test system, but on the actual server we get the following error
during the restore:
Thank you very much, I was not aware of the 'ONLY' clause.
Nuwan.
Tom Lane <[EMAIL PROTECTED]> wrote: Nuwan Liyanage writes:
> Now I added the trigger rule to base_table and the data for
> partition_3 is going to the right place, but I am stuck with some data
> in the actual base_t
Nuwan Liyanage <[EMAIL PROTECTED]> writes:
> Now I added the trigger rule to base_table and the data for
> partition_3 is going to the right place, but I am stuck with some data
> in the actual base_table. How could I move that data from the base
> table to the partition_3?
Somethi
Question: I have a base table with several temporal partitions like this:
base_table
partition_1
partition_2
There are check rules on partitions, and trigger rules on the base
table to ensure data loaded into base_table goes to a correct
partition.
I added part
On Mon, Mar 3, 2008 at 3:55 AM, Vladimir Rusinov <[EMAIL PROTECTED]>
wrote:
> How can I check if all indexes in my database is valid, how to show the
> invalid ones (and rebuild them)?
> Any quick solutions?
How do you define whether and index is valid or invalid?
--
Regards,
Richard Broersma
On Sonntag, 2. März 2008 Hannes Dorbath wrote:
> That's great, I missed it. May I suggest to add a warning about LVM,
> EVMS, DRBD and Linux MD RAID 5? All do currently not support write
> barriers and are therefor not safe with volatile write caches below.
And what about VMware, XEN, etc., used o
Hello!
How can I check if all indexes in my database is valid, how to show the
invalid ones (and rebuild them)?
Any quick solutions?
Thanks.
--
Vladimir Rusinov
Voronezh, Russia
