On Saturday, January 28, 2017, Rita wrote:
> After xmltest has been populated, I can run xpath and unest to get my data
> into a row but I would like to store that result in another table, I am
> guessing I should look into triggers for something like that?
>
I suspect that using xpath in the da
I want to over write the data because I don't need to keep its history.
Yes, the 5-6 table will be the subset of the data. The subset of the data
will all come from xpath. I don't want to keep doing an xpath query when a
client requests the data.
On Sun, Jan 29, 2017 at 5:42 PM, Adrian Klaver
OK. I think I'm on to something here, I first reset back to my file level
backup.
I created a recovery.conf file in the root of the data directory like this:
-
restore_command = 'cp /mnt/archive/%f %p'
recovery_target_time = '2017-01-24 02:08:00.023064+11'
recovery_target_inclus
On 01/28/2017 05:57 PM, Rita wrote:
sorry for the late reply.
My table schema is very simple
DROP TABLE xmltest;
create table xmltest(
id serial,-- dont really need the serial
Maybe not a serial id, but a Primary Key of some sort would help with
what you say you want to do b
On 01/28/2017 11:23 PM, Brian Mills wrote:
I presume this is a binary log file for the database.
Am I able to recover to a point in time using this log file?
What I would do in SQL Server would be recover to a point in time, say a
bit before the last completed transaction time the log mentions,
On 01/28/2017 11:23 PM, Brian Mills wrote:
I presume this is a binary log file for the database.
Am I able to recover to a point in time using this log file?
What I would do in SQL Server would be recover to a point in time, say a
bit before the last completed transaction time the log mentions,