r the join and could improve performance.
Best Regards
Mikael Krantz
On Tue, Dec 14, 2010 at 7:42 PM, Ng, Stan wrote:
> Ah, I forgot to mention why I suspected corruption. The delta
> application is a single threaded, sequential process. Each delta is done
> within a single transaction. If
his error and decide what the proper action
to take is; it might be ignoring the second insert, it might be
updating the already existing row with that key or something else
entirely, depending on your application.
Best Regards
Mikael Krantz
On Tue, Dec 14, 2010 at 3:18 AM, Ng, Stan wrote:
> I’v
This is not a bug. Each query requires a round-trip to the server so
it is natural that a lot of queries take additional time.
/M
On Wed, Jul 29, 2009 at 1:01 PM, Axel Fix wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4954
> Logged by: Axel Fix
> Email addr
It might be that your column may be NULL as well as TRUE or FALSE. I
am no expert in this matter though.
/M
On Fri, Jul 17, 2009 at 10:12 AM, Jan-Ivar
Mellingen wrote:
> One of our customers discovered that by replacing <>TRUE with =FALSE in
> a query of a table containing 750.000 records reduced
On Fri, May 15, 2009 at 2:26 PM, Heikki Linnakangas
wrote:
> That was the original issue you ran into. That has now been fixed by forcing
> an xlog switch at pg_start_backup(), so that you can't start a backup in a
> WAL file that contains records from a lower numbered timeline.
Ah, sorry.
/M
-
On Fri, May 15, 2009 at 2:22 PM, Simon Riggs wrote:
> Let's document that timeline files should not be deleted from the
> archive iff there exists a base backup made during a lower numbered
> timeline.
Or made during a higher numbered timeline which happens to start in a
WAL-file containing recor
On Wed, May 6, 2009 at 6:26 PM, Heikki Linnakangas
wrote:
>> How to reproduce:
>>
>> * restore from backup
>> * SELECT pg_start_backup('label');
>> * take a new backup
>> * SELECT pg_stop_backup();
>> * copy the relevant WAL-files
>> * try to restore the backup
>
> I failed to reproduce this
The following bug has been logged online:
Bug reference: 4796
Logged by: Mikael Krantz
Email address: m...@zigamorph.se
PostgreSQL version: 8.3.7-0lenny1
Operating system: Linux (debian lenny)
Description:Recovery followed by backup creates unrecoverable
WAL-file
