On 01/29/2017 03:12 PM, Brian Mills wrote:
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-
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 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,
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, then take
a backup. Is that possible in post
I have a consistent sql dump from 24 hour previous.
The file level backup was done with rsync -a of full data directory after
the issue occurred so could reset as I learned.
Brian
On Sun, 29 Jan 2017 at 9:18 am, Adrian Klaver
wrote:
> On 01/28/2017 01:55 PM, Brian Mills wrote:
> > Yes, its th
On 01/28/2017 01:55 PM, Brian Mills wrote:
Yes, its the last one in the directory, pg_xlog directory
...more files...
-rw--- 1 postgres postgres 16777216 Jan 21 10:05
0001000500A1
-rw--- 1 postgres postgres 16777216 Jan 22 21:29
0001000500A2
-rw--- 1 postgr
Yes, its the last one in the directory, pg_xlog directory
...more files...
-rw--- 1 postgres postgres 16777216 Jan 21 10:05
0001000500A1
-rw--- 1 postgres postgres 16777216 Jan 22 21:29
0001000500A2
-rw--- 1 postgres postgres 16777216 Jan 24 02:08
0001000
Hello Brian,
On Sun, 2017-01-29 at 07:16 +1100, Brian Mills wrote:
> Hi,
>
> No, it hasn't changed since the first time I looked at it.
>
> root@atlassian:/home/tbadmin# ps ax | grep post
> 1364 ? Ss 0:00 /usr/lib/postfix/master
> 5198 pts/3 S 0:00 su postgres
> 5221 pts/3
Hi,
No, it hasn't changed since the first time I looked at it.
root@atlassian:/home/tbadmin# ps ax | grep post
1364 ?Ss 0:00 /usr/lib/postfix/master
5198 pts/3S 0:00 su postgres
5221 pts/3S 0:00 /usr/lib/postgresql/9.3/bin/postgres -D
/etc/postgresql/9.3/main
522
On 01/27/2017 05:40 PM, Brian Mills wrote:
First of all, Thank you for your time to assist me learning. I really
appreciate it.
root# ps ax | grep post
1364 ?Ss 0:00 /usr/lib/postfix/master
5198 pts/3S 0:00 su postgres
5221 pts/3S 0:00 /usr/lib/postgresql/9.3/bin
First of all, Thank you for your time to assist me learning. I really
appreciate it.
root# ps ax | grep post
1364 ?Ss 0:00 /usr/lib/postfix/master
5198 pts/3S 0:00 su postgres
5221 pts/3S 0:00 /usr/lib/postgresql/9.3/bin/postgres -D
/etc/postgresql/9.3/main
5222 ?
On 01/27/2017 01:31 PM, Brian Mills wrote:
Hi,
I have a Atlassian Confluence Wiki that depends on postgres, but I
haven't much experience with postgres other than for this purpose.
A few days ago, the hard disk filled, so all services stopped working.
When the admin realised this he increased t
Hi,
I have a Atlassian Confluence Wiki that depends on postgres, but I haven't
much experience with postgres other than for this purpose.
A few days ago, the hard disk filled, so all services stopped working.
When the admin realised this he increased the disk size (its in a cloud, so
that was eas
14 matches
Mail list logo