Skip site navigation (1) Skip section navigation (2)

POSTGRES WAL

From: Mageshwaran <j_mageshwaran(at)sifycorp(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Chad Wagner <chad(dot)wagner(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, deductive(at)kutoma(dot)com
Subject: POSTGRES WAL
Date: 2007-03-01 03:31:21
Message-ID: 45E64909.8080201@sifycorp.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi ,

Is there any method or utility to convert content of WAL files into 
Human Readable format.



Regards
J Mageshwaran






Andrew Dunstan wrote:

> Chad Wagner wrote:
>
>> On 2/26/07, *Josh Berkus* <josh(at)agliodbs(dot)com 
>> <mailto:josh(at)agliodbs(dot)com>> wrote:
>>
>>     > Just wondering after reading so many mails from Hackers
>>     List.(its 2.15 AM
>>     > now!!) Is there anybody working on something to create a DB from
>>     > a) The TODO list http://www.postgresql.org/docs/faqs.TODO.html
>>     > b) The sourcecode of PostgreSQL
>>     > c) The relevant Mailings from the developers lists
>>
>>     Of those, only the TODO makes sense as a DB.  You're welcome to go
>>     for it.
>>
>> The TODO list is a bit outdated, and it would make sense to make it 
>> into a web page and assign names to the tasks and which releases the 
>> TODO task will make it in.  Perhaps it would even be useful for folks 
>> to post their WIP patches, status updates, etc to such a page?
>>
>> Any comments?  I am willing to chip in.  I could only imagine the 
>> current workload for maintaining this is a bit overwhelming.
>
>
> Before we rehash recent debates, please, everybody, review them. Going 
> over and over and over the same ground laboriously is really getting 
> tiresome, and unfortunately it's also getting more frequent. It's 
> *déjà vu *all over again.
>
> And, for the record, I do not see the slightest point in putting the 
> TODO list on its own into a database. None, zilch, nada. As database 
> professionals we should be adept at recognising when the use of a 
> database is appropriate and when it isn't. If we put it into a 
> tracking system (presumably database backed) that would be another 
> matter, but that has gone nowhere as usual.
>
> There is some point in putting it in a wiki where we can gather 
> relevant documents, links to discussions etc. That's why the 
> developers' wiki was established, AIUI.
>
> cheers
>
> andrew
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>       message can get through to the mailing list cleanly



********** DISCLAIMER **********
Information contained and transmitted by this E-MAIL is proprietary to 
Sify Limited and is intended for use only by the individual or entity to 
which it is addressed, and may contain information that is privileged, 
confidential or exempt from disclosure under applicable law. If this is a 
forwarded message, the content of this E-MAIL may not have been sent with 
the authority of the Company. If you are not the intended recipient, an 
agent of the intended recipient or a  person responsible for delivering the 
information to the named recipient,  you are notified that any use, 
distribution, transmission, printing, copying or dissemination of this 
information in any way or in any manner is strictly prohibited. If you have 
received this communication in error, please delete this mail & notify us 
immediately at admin(at)sifycorp(dot)com


Watch the latest updates on Mumbai, with video coverage of news, events,
Bollywood, live darshan from Siddhivinayak temple and more, only on
www.mumbailive.in

Watch the hottest videos from Bollywood, Fashion, News and more only on
www.sifymax.com


In response to

Responses

pgsql-hackers by date

Next:From: Jonah H. HarrisDate: 2007-03-01 03:34:21
Subject: Re: COMMIT NOWAIT Performance Option
Previous:From: Jonah H. HarrisDate: 2007-03-01 03:06:00
Subject: Re: COMMIT NOWAIT Performance Option

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group