Vick Khera wrote:
> On Fri, Oct 23, 2009 at 6:44 PM, Sydney Puente wrote:
>> Ah I see what you mean - thanks very much that is v helpful!
>> Yes the copy will be read-only.
>> Will have 3 tables of data, being read (readonly) and in the background
>> Will have 3 shadow tables populated from an unr
On Fri, Oct 23, 2009 at 6:44 PM, Sydney Puente wrote:
> Ah I see what you mean - thanks very much that is v helpful!
> Yes the copy will be read-only.
> Will have 3 tables of data, being read (readonly) and in the background
> Will have 3 shadow tables populated from an unreliable db over an unrel
On Fri, Oct 23, 2009 at 2:45 AM, Sydney Puente wrote:
> This data will be accessed a couple of times a second, and I have a cunning
> plan to have a view that points to the initial dataload, and then load up
> the new data into a shadow table, drop the view and then recreate it
> pointing to the
On Fri, Oct 23, 2009 at 2:45 AM, Sydney Puente wrote:
> This data will be accessed a couple of times a second, and I have a cunning
> plan to have a view that points to the initial dataload, and then load up
> the new data into a shadow table, drop the view and then recreate it
> pointing to the
Hello,
I have a requirement to pull 2 tables of data from an unreliable db and stash
the data in postgres on redhat.
Dont imagine the initial load will be be too difficult, gonna use perl DBD to
get the data. < 100 000 records in total , 10 -15 fields.
needs sync-ing regularly - every 12 hours
