On 04.03.2011 23:28, Kevin Grittner wrote:
I wrote:
I think what we're protecting against is disk I/O at COMMIT time,
not transaction startup.
One more thought on this -- on a properly configured server, this
code should rarely be exercised unless there is a long-running READ
WRITE transactio
This is currently a TODO so at least we are tracking it.
---
andreas wrote:
> On Tue, 2010-10-19 at 18:22 -0400, Tom Lane wrote:
> > Robert Haas writes:
> > > On Mon, Oct 11, 2010 at 7:50 PM, Tom Lane wrote:
> > >> Well, a
2011/3/5 Domčeky-Záhradné :
> Good morning,
> I was to install latest installation of your application:
> postgresql-9.0.3-1-windows.exe to my PC ,
> but there occored Error that you can see in attachment. I have Windows 7 -
> 32 bit system
> Thank you for answer.
That error comes from the Micro
Good morning,
I was to install latest installation of your application:
postgresql-9.0.3-1-windows.exe to my PC ,
but there occored Error that you can see in attachment. I have Windows 7 - 32
bit system
Thank you for answer.
DOMČEKY-ZÁHRADNÉ
Ing. Jozef Hrčka
Jánskeho 12, 949 01 NITRA
tel:
The following bug has been logged online:
Bug reference: 5916
Logged by: Allan Registos
Email address: allan.regis...@smpc.steniel.com.ph
PostgreSQL version: 9.0.0-1-linux
Operating system: Fedora 14
Description:PGAdmin crash
Details:
When I press the SQL query, the
On Thu, 3 Mar 2011 10:20:06 -0500
Robert Haas wrote:
[snip]
> It seems like there are a lot of possible combinations here that could
> be useful, so we'd want something that allowed a fairly flexible
> specification of what to match.
>
> Is this a problem you're interested in working on (i.e. co
