Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Constant WAL replay
- From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
- To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
- Cc: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org, eg(at)cybertec(dot)at
- Subject: Re: Constant WAL replay
- Date: Mon, 25 Apr 2005 13:08:57 -0700
- Message-id: <426D4E59(dot)1010302(at)commandprompt(dot)com>
What really interests me here: Where is you code located in order to make sure that this things can work reliably?We are integrated into the PostgreSQL backend.So they have to get a new PostgreSQL release from you for every minor upgrade, I assume at no cost?
Yep :) Sincerely, Joshua D. Drake Command Prompt, Inc.
-- Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240 PostgreSQL Replication, Consulting, Custom Programming, 24x7 support Managed Services, Shared and Dedication Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
- References:
- Re: Constant WAL replay
- From: Bruce Momjian
- Re: Constant WAL replay
- Prev by Date: Re: Constant WAL replay
- Next by Date: Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
- Previous by thread: Re: Constant WAL replay
- Next by thread: Re: Constant WAL replay
- Indexes: