I tried that when I was testing .. if I stopped at the most recent
insert/update/delete previous to the drop database (with telling it to
include the change) it DIDN'T include the change (I assume because the
commit timestamp was slightly after the transaction timestamp) .. and if I
told it to stop
On 12/03/2014 03:52 PM, Joshua Boyd wrote:
I tried that when I was testing .. if I stopped at the most recent
insert/update/delete previous to the drop database (with telling it to
include the change) it DIDN'T include the change (I assume because the
commit timestamp was slightly after the trans
On 12/02/2014 03:50 PM, Joshua Boyd wrote:
Having continued my research, the problem I encountered is the exact
same that's been recorded here:
https://www.marshut.net/kstxxk/pitr-failing-to-stop-before-drop-database.html
I think I answered all the questions - please let me know if I missed
On 12/02/2014 03:50 PM, Joshua Boyd wrote:
Having continued my research, the problem I encountered is the exact
same that's been recorded here:
https://www.marshut.net/kstxxk/pitr-failing-to-stop-before-drop-database.html
I took the backup by following the procedures as laid forth in the
cont
Having continued my research, the problem I encountered is the exact same
that's been recorded here:
https://www.marshut.net/kstxxk/pitr-failing-to-stop-before-drop-database.html
I took the backup by following the procedures as laid forth in the
continuous archiving document (
http://www.postgre
On 11/28/2014 02:29 PM, Joshua Boyd wrote:
I am testing out point in time recovery from a hot physical backup in a
disaster recovery situation - I turned on archiving of files, created a
hot physical backup,
How did you take the backup?
Archiving how and to where?
then (after letting it run f
I am testing out point in time recovery from a hot physical backup in a
disaster recovery situation - I turned on archiving of files, created a hot
physical backup, then (after letting it run for a few days) issued a "DROP
DATABASE". The pg_log file shows the DROP DATABASE command was issued at
'2
On Tue, Aug 27, 2013 at 2:26 PM, pg noob wrote:
>
> Hi all,
>
> I recently ran a couple of tests where I took one of my production
> systems and did a drop-in replacement of postgres 8.4 with 9.2.4.
> I was expecting to see some performance improvement given the release
> notes describing 9.2 as a
On 08/27/2013 02:26 PM, pg noob wrote:
Hi all,
I recently ran a couple of tests where I took one of my production
systems and did a drop-in replacement of postgres 8.4 with 9.2.4.
I was expecting to see some performance improvement given the release
notes describing 9.2 as a "largely performanc
Hi all,
I recently ran a couple of tests where I took one of my production
systems and did a drop-in replacement of postgres 8.4 with 9.2.4.
I was expecting to see some performance improvement given the release
notes describing 9.2 as a "largely performance related release".
At least for my appli
What's the current status on installs of PostGis with Postgres 9.2? Can I run
PostGIS 1.5 and/or PostGIS 2.0 with Postgres 9.2?
I noticed StackBuilder does not include PostGis with Postgres 9.2, but does
include it (PostGis 1.5) with Postgres 9.1.
I'm running Postgres 9.1 on a Mac OSX 10.7 (In
Original message:
De : pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] De la part de Marc Watson
Envoyé : June-11-12 8:36 AM
À : Craig Ringer
Cc : pgsql-general@postgresql.org; dp...@pgadmin.org;
sachin.srivast...@enterprisedb.com
Objet : Re: [GENERAL] Postgres
[CCed the list]
On Tue, Jun 12, 2012 at 12:33 PM, Sachin Srivastava <
sachin.srivast...@enterprisedb.com> wrote:
>
> On Tue, Jun 12, 2012 at 12:31 PM, Craig Ringer wrote:
>
>> On 06/11/2012 08:36 PM, Marc Watson wrote:
>>
>>>
>>> *De :*Craig Ringer [mailto:ring...@ringerc.id.au]
>>>
>>>
>>>
>>> I
De : Craig Ringer [mailto:ring...@ringerc.id.au]
Envoyé : June-09-12 3:50 AM
(CCing Dave Page & Sachin Srivastava who work on the installer):
Short version is that the Pg installer appears to need to:
- Include the latest release of the redist because there's a security fix in it
- use /passi
(CCing Dave Page & Sachin Srivastava who work on the installer):
Short version is that the Pg installer appears to need to:
- Include the latest release of the redist because there's a security
fix in it
- use /passive not /q when invoking it
- treat return 5100 as success
- swear at Microsoft
De : Craig Ringer [mailto:ring...@ringerc.id.au]
Envoyé : June-08-12 9:20 AM
On 06/08/2012 08:04 PM, Marc Watson wrote:
Thanks, Craig
It was failing on vcredist_x86 and vcredist_x64, because I had newer versions
installed (10.0.40219). After uninstalling them, all is OK.
Oooh! That should
On 06/08/2012 08:04 PM, Marc Watson wrote:
Thanks, Craig
It was failing on vcredist_x86 and vcredist_x64, because I had newer
versions installed (10.0.40219). After uninstalling them, all is OK.
Oooh! That shouldn't happen. At all. The vc redists should, as far as I
know, either:
(a) Si
Objet : Re: [GENERAL] Postgres 9.2 beta2 one-click installer on windows
On 06/07/2012 10:00 PM, Marc Watson wrote:
Hi all,
Just a note that the 32 and 64-bit installers fail on windows 7 64-bit with the
error 'An error occurred executing the Microsoft VC++ runtime installer.'. T
On 06/07/2012 10:00 PM, Marc Watson wrote:
Hi all,
Just a note that the 32 and 64-bit installers fail on windows 7 64-bit
with the error 'An error occurred executing the Microsoft VC++ runtime
installer.'. The beta-1 32-bit installer works OK.
Well, they fail on your particular Windows 7
Hi all,
Just a note that the 32 and 64-bit installers fail on windows 7 64-bit
with the error 'An error occurred executing the Microsoft VC++ runtime
installer.'. The beta-1 32-bit installer works OK.
- Mark Watson
20 matches
Mail list logo
