Kevin Grittner [EMAIL PROTECTED] writes:
Attached is a version as good as I know how to get it.
It works for us, so barring any problems as we use it, I'm done.
I finally got around to looking at this. Neither err.h nor err()
are portable (they're not in the Single Unix Spec, and they don't
On Sun, Sep 9, 2007 at 4:16 AM, apoc9009 [EMAIL PROTECTED] wrote:
No! Actually I'm wearing my tin hat right now and I Never say Anything
about My Suspicions about 9/11 on Internet in fear of Echelon catching
and filing me.
---
Hannu
hmm, a little bit Para?
It seems there is already a project on pgfoundry but there are no files:
http://pgfoundry.org/projects/clearxlogtail/
Should this be on pgfoundry or in the Postgres distribution. It seems
it might be tied enough to the WAL format to be in the Postgres
distribution.
On Thu, Sep 27, 2007 at 4:59 PM, in message
[EMAIL PROTECTED], Kevin Grittner
[EMAIL PROTECTED] wrote:
By the way, I realize that the error messages are still lame.
I'm going to do something about that.
Attached is a version as good as I know how to get it.
It works for us, so barring
On Wed, 2007-09-26 at 16:31 -0500, Kevin Grittner wrote:
The one downside I've found is that it adds 0.2
seconds of CPU time per WAL file archive during our heaviest update
periods. It's in the archiver process, not a backend process that's
running a query, and we're not generally CPU bound,
On Thu, Sep 27, 2007 at 6:56 AM, in message
[EMAIL PROTECTED], Simon Riggs [EMAIL PROTECTED]
wrote:
On Wed, 2007-09-26 at 16:31 -0500, Kevin Grittner wrote:
The one downside I've found is that it adds 0.2
seconds of CPU time per WAL file archive during our heaviest update
periods.
OK,
On Wed, Sep 26, 2007 at 7:29 PM, in message [EMAIL PROTECTED],
Florian G. Pflug [EMAIL PROTECTED] wrote:
Kevin Grittner wrote:
I omitted the code I was originally considering to have it work against
files in place rather than as a filter. It seemed much simpler this
way, we didn't actually
On Thu, Sep 27, 2007 at 6:56 AM, in message
[EMAIL PROTECTED], Simon Riggs [EMAIL PROTECTED]
wrote:
On Wed, 2007-09-26 at 16:31 -0500, Kevin Grittner wrote:
The one downside I've found is that it adds 0.2
seconds of CPU time per WAL file archive during our heaviest update
periods. It's
On Mon, Sep 24, 2007 at 4:17 PM, in message
[EMAIL PROTECTED], Kevin Grittner
[EMAIL PROTECTED] wrote:
On Thu, Sep 6, 2007 at 7:03 PM, in message
[EMAIL PROTECTED], Jeff Davis [EMAIL PROTECTED]
wrote:
I think ... there's still room for a simple tool that can zero out
the meaningless
On Wed, 2007-09-26 at 11:05 -0500, Kevin Grittner wrote:
Lacking any suggestions, I plowed ahead with something which satisfies
our needs. First, rough, version attached. It'll save us buying another
drawer of drives, so it was worth a few hours of research to figure out
how to do it.
On Wed, Sep 26, 2007 at 3:14 PM, in message
[EMAIL PROTECTED], Simon Riggs [EMAIL PROTECTED]
wrote:
It's nicely written
Thanks. I spent some time looking at Tom Lane's pg_resetxlog and the
source code for cat to model my code. I'm rather rusty on C, so I wanted
to minimize the chance of
On Wed, Sep 26, 2007 at 3:14 PM, in message
[EMAIL PROTECTED], Simon Riggs [EMAIL PROTECTED]
wrote:
The logic for zeroing the blocks makes me nervous. It doesn't locate the
block from which to start, it treats all blocks equally, so might zero
some blocks and not others. What you have
Kevin Grittner wrote:
I omitted the code I was originally considering to have it work against
files in place rather than as a filter. It seemed much simpler this
way, we didn't actually have a use case for the additional functionality,
and it seemed safer as a filter. Thoughts?
A special
On Thu, Sep 6, 2007 at 7:31 PM, in message
[EMAIL PROTECTED], Kevin Grittner
[EMAIL PROTECTED] wrote:
On Thu, Sep 6, 2007 at 7:03 PM, in message
[EMAIL PROTECTED], Jeff Davis [EMAIL PROTECTED]
wrote:
I think ... there's still room for a simple tool that can zero out
the meaningless
Joshua D. Drake schrieb:
This is not acceptable on our lists. Do not post in such a way again.
Sincerely,
Joshua D. Drake
Hi Josh,
Your're right, but this special Guy has just boring me a lot with
Replication Things but
my [Featurerequest] on the Topic was dedicated to Streaming
Ühel kenal päeval, L, 2007-09-08 kell 10:39, kirjutas apoc9009:
Joshua D. Drake schrieb:
This is not acceptable on our lists. Do not post in such a way again.
Sincerely,
Joshua D. Drake
Hi Josh,
Your're right, but this special Guy has just boring me a lot with
Replication Things
C. 'backup _is_ replication' is also true
--
Hannu
It is useless to speak with a person like you about the diffrence between
Backup and Replications.Both Things having diffrent Concepts and
Approaches,
but for you it is all the same.
What should i say? Thadts the typically
Ühel kenal päeval, L, 2007-09-08 kell 21:15, kirjutas Apoc Sagdiyev:
C. 'backup _is_ replication' is also true
--
Hannu
It is useless to speak with a person like you
Oh, you think that _I_ am scandinavian ?? Never thought about that
possibility ;P
If speaking with me is
No! Actually I'm wearing my tin hat right now and I Never say Anything
about My Suspicions about 9/11 on Internet in fear of Echelon catching
and filing me.
---
Hannu
hmm, a little bit Para?
http://www.myvideo.de/watch/1776449
Ok, now your point of View its more clearly...
Hi,
apoc9009 wrote:
Thadt is Replication NOT Backup
I've now read all of your messages in this thread, but I simply fail to
understand why you are that much opposed to the term 'replication'. I
think the only thing which comes any close to what you're looking for is
replication (in
backup is not replication.
but replicated database can be treated as good source of backup.
please take following remarks:
1) in English you don't capitalize nouns
2) read what other people write to you and try to understand that.
3) this is open source, try to be more cooperative not just cry
apoc9009 wrote:
Write it down 100 times and maybe you understand
If you are going to be rude nobody will bother to respond to you.
Acknowledged experts have been very patient with you so far in this
thread. You should be appreciative, not truculent.
cheers
andrew
Markus Schiltknecht wrote:
[2]: Terms and Definitions of Database Replication
http://www.postgres-r.org/documentation/terms
Markus, the links in the left side menu are broken on the about and
documentation page. They point to http://www.postgres-r.org/overview
instead of
Markus Schiltknecht schrieb:
Hi,
apoc9009 wrote:
Thadt is Replication NOT Backup
I've now read all of your messages in this thread, but I simply fail
to understand why you are that much opposed to the term 'replication'.
I think the only thing which comes any close to what you're looking
Ühel kenal päeval, R, 2007-09-07 kell 12:03, kirjutas apoc9009:
Andrew Sullivan schrieb:
It seems that what you want is near-real-time online backups with _no
cost_, which is not a feature that I think anyone will ever work on.
A
100% Correct!
I think anyone commit the Statement,
Ühel kenal päeval, R, 2007-09-07 kell 12:20, kirjutas apoc9009:
Trevor Talbot schrieb:
Backup 12/24/2008 Version 2
/pg/backup/12_24_2008/base/rcvry.rcv--- Basebackup
/pg/backup/12_24_2008/changes/0001.chg --- Changed Data
/changes/0002.chg --- Changed Data
Hi,
apoc9009 wrote:
Translation for you:
A Backup is a File or Set of Files thadt contains the Data of your
Business critical Informations.
It should not be Archived on the same place, the same House or the same
Room.
I disagree, a backup does not necessarily have to be a single file or a
Filip Rembiałkowski schrieb:
please take following remarks:
thx, but if i need some advice form a scandinavian dickhead then i will
let you know this
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
apoc9009 wrote:
Filip Rembiałkowski schrieb:
please take following remarks:
thx, but if i need some advice form a scandinavian dickhead then i will
let you know this
This is not acceptable on our lists. Do not post in such a way again.
apoc9009 wrote:
Filip Rembiałkowski schrieb:
please take following remarks:
thx, but if i need some advice form a scandinavian dickhead then i will
let you know this
That kind of remark is not acceptable on the PostgreSQL mailing lists.
Please do not post here again unless you can speak to
On Fri, Sep 07, 2007 at 12:03:31PM +0200, apoc9009 wrote:
Andrew Sullivan schrieb:
It seems that what you want is near-real-time online backups with _no
cost_, which is not a feature that I think anyone will ever work on.
A
100% Correct!
I think anyone commit the Statement, thadt a
Trevor Talbot schrieb:
Backup 12/24/2008 Version 2
/pg/backup/12_24_2008/base/rcvry.rcv--- Basebackup
/pg/backup/12_24_2008/changes/0001.chg --- Changed Data
/changes/0002.chg --- Changed Data
/changes/0003.chg --- Changed Data
Andrew Sullivan schrieb:
It seems that what you want is near-real-time online backups with _no
cost_, which is not a feature that I think anyone will ever work on.
A
100% Correct!
I think anyone commit the Statement, thadt a Databases is a very
imported Part of Software
for a wide range of
Ühel kenal päeval, R, 2007-09-07 kell 16:41, kirjutas apoc9009:
Filip Rembiałkowski schrieb:
please take following remarks:
thx, but if i need some advice form a scandinavian dickhead then i will
let you know this
Is this apoc9009 guy real ?
For some time I honestly believed (based in part
On Sat, Sep 08, 2007 at 01:02:04AM +0300, Hannu Krosing wrote:
??hel kenal p??eval, R, 2007-09-07 kell 16:41, kirjutas apoc9009:
Filip Rembia??kowski schrieb:
please take following remarks:
thx, but if i need some advice form a scandinavian dickhead then i will
let you know this
Is
apoc9009 wrote:
Hi Hackers,
In my Project i have to handle a Database with 600 GByte Text only,
distributed on 4 Tablespaces
on multiple Harddisks and Remote SAN's connected via Gigaethernet to the
Remote SAN-Storage.
I need more flexibility by doing Backups of my big Database, but the
http://www.postgresql.org/docs/8.2/static/warm-standby.html
Particularly section 23.4.4
Thadt is Replication NOT Backup
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
http://www.postgresql.org/docs/8.2/static/warm-standby.html
Particularly section 23.4.4
23.4.4 is thadt what iam using just im Time but this ist not eneought
for me!
No Versioning, no chances to prevent data losses
You have to wait until a WAL File ist written (Default Value for WAL
apoc9009 wrote:
http://www.postgresql.org/docs/8.2/static/warm-standby.html
Particularly section 23.4.4
23.4.4 is thadt what iam using just im Time but this ist not eneought
for me!
No Versioning, no chances to prevent data losses
You have to wait until a WAL File ist written (Default
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
I have read this:
PostgreSQL directly supports file-based log shipping as described above.
It is also possible to implement record-based log shipping, though
apoc9009 wrote:
I wish to have an Solution, thadt backup my Database DB wihout
Datalosses, without locking Tables, without Shutdown
and without any User must be forced for logging out (Backup in
Production State Online without Datalosses).
Without datalosses is utopy. For that, you'd need
Hi,
On 9/6/07, apoc9009 [EMAIL PROTECTED] wrote:
Filebased Logship backups having a big Problem for doing continous
Backups. You have to wait until
the Postmaster has written the WAL File, after this you can save it to
the Backupserver. But 1 WAL
has a size of 16 MByte ny default! (thadt is
apoc9009 wrote:
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
I have read this:
PostgreSQL directly supports file-based log shipping as described above.
It is also possible to implement record-based log
Ühel kenal päeval, N, 2007-09-06 kell 12:53, kirjutas apoc9009:
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
I have read this:
PostgreSQL directly supports file-based log shipping as described above.
On Thu, 2007-09-06 at 12:21 +0200, apoc9009 wrote:
If the System Crash, you have Dataloss of
over 16 MBytes thats Fatal and not acceptable! 1MByte Dataloss of ASCII Data
is also
not acceptable!
Is any data loss acceptable in the case of a disaster? How much?
--
Simon Riggs
Ühel kenal päeval, N, 2007-09-06 kell 12:53, kirjutas apoc9009:
I wish to have an Solution, thadt backup my Database DB wihout
Datalosses,
Then you need the backup record to be completed on the backup machine
before the transaction commit returns on master.
This is quaranteed to be really
So you want the user to still be connected to the failed machine, but at
the same time be connected to the new live failover machine ?
-
Hannu
No.
The User should be connected to the running db without restrictions
while backup is in progress
Apoc
---(end of
Ühel kenal päeval, N, 2007-09-06 kell 16:15, kirjutas apoc9009:
So you want the user to still be connected to the failed machine, but at
the same time be connected to the new live failover machine ?
-
Hannu
No.
The User should be connected to the running db without restrictions
On Thu, 2007-09-06 at 12:53 +0200, apoc9009 wrote:
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
I have read this:
PostgreSQL directly supports file-based log shipping as described above.
It is also
Heikki Linnakangas schrieb:
apoc9009 wrote:
Without datalosses is utopy. For that, you'd need something like
synchronous replication, otherwise you're always going to have a window
where you have something committed in the server, but not yet in the
backup. So it's just a question of how wide
Simon Riggs schrieb:
On Thu, 2007-09-06 at 12:53 +0200, apoc9009 wrote:
You've either not read 23.4.4 or haven't understood it. If the text is
unclear, documentation additions/changes are always welcome.
I have read this:
PostgreSQL directly supports file-based log shipping as
On 9/6/07, apoc9009 [EMAIL PROTECTED] wrote:
Backup 12/24/2008 Version 2
/pg/backup/12_24_2008/base/rcvry.rcv --- Basebackup
/pg/backup/12_24_2008/changes/0001.chg --- Changed Data
/changes/0002.chg --- Changed Data
On Thu, Sep 06, 2007 at 04:08:10PM +0200, apoc9009 wrote:
archive_timeout setting. It will produce a lot of log files with very
little content in them, but they will compress well.
Yes, it is possible but not recommended . My Backup Servers Filesystem
will explode :D
. . .
Correct, but
On Thu, 2007-09-06 at 12:08 +0100, Heikki Linnakangas wrote:
With file-based log shipping, you can get down to 1 second, by using the
archive_timeout setting. It will produce a lot of log files with very
little content in them, but they will compress well.
I tried doing a couple
On Thu, 2007-09-06 at 17:53 +0300, Hannu Krosing wrote:
Ühel kenal päeval, N, 2007-09-06 kell 16:15, kirjutas apoc9009:
So you want the user to still be connected to the failed machine, but at
the same time be connected to the new live failover machine ?
-
Hannu
No.
The
Ühel kenal päeval, N, 2007-09-06 kell 19:33, kirjutas apoc9009:
Simon Riggs schrieb:
I'm not clear whether you are looking for Backup, or High Availability
Replication.
There is no data loss with the online backup technique described in the
manual.
No, there is a lost of Data.
Jeff Davis [EMAIL PROTECTED] writes:
On Thu, 2007-09-06 at 12:08 +0100, Heikki Linnakangas wrote:
With file-based log shipping, you can get down to 1 second, by using the
archive_timeout setting. It will produce a lot of log files with very
little content in them, but they will compress well.
On Thu, Sep 6, 2007 at 7:03 PM, in message
[EMAIL PROTECTED], Jeff Davis [EMAIL PROTECTED]
wrote:
I think ... there's still room for a simple tool that can zero out
the meaningless data in a partially-used WAL segment before compression.
It seems reasonable to me, so long as you keep
On Thu, 2007-09-06 at 21:50 +0100, Gregory Stark wrote:
- Improve scalability of recovery for large I/O bound databases
That seems too vague for the TODO. Did you have specific items in mind?
I think we should parallelise recovery. Heikki wanted to do this another
way, so I worded it
Simon Riggs [EMAIL PROTECTED] writes:
High Availability
-
- Allow a warm standby system to also allow read-only statements
- Allow WAL traffic to be streamed to another server for stand-by
replication (synchronous/asynchronous options)
Asynchronous streaming of WAL would be
On Thu, 2007-09-06 at 19:23 -0400, Tom Lane wrote:
Jeff Davis [EMAIL PROTECTED] writes:
On Thu, 2007-09-06 at 12:08 +0100, Heikki Linnakangas wrote:
With file-based log shipping, you can get down to 1 second, by using the
archive_timeout setting. It will produce a lot of log files with very
On Thu, Sep 6, 2007 at 3:25 PM, in message
[EMAIL PROTECTED], Jeff Davis [EMAIL PROTECTED]
wrote:
On Thu, 2007-09-06 at 12:08 +0100, Heikki Linnakangas wrote:
With file-based log shipping, you can get down to 1 second, by using the
archive_timeout setting. It will produce a lot of log files
62 matches
Mail list logo
