On Thursday, 20 March 2014 2:45 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Wed, Mar 19, 2014 at 6:25 AM, Wang, Jing ji...@fast.au.fujitsu.com wrote:
On Friday, 14 March 2014 2:42 PM, Amit Kapila amit.kapil...@gmail.com
wrote:
I think it might be okay to even change this API to return
On Friday, 14 March 2014 2:42 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Wed, Mar 12, 2014 at 12:22 PM, Haribabu Kommi kommi.harib...@gmail.com
wrote:
On Tue, Mar 11, 2014 at 2:59 PM, Amit Kapila amit.kapil...@gmail.com wrote:
By the way have you checked if FreeSpaceMapVacuum() can
Hi
Enclosed is the patch to implement the requirement that issue log
message to suggest VACUUM FULL if a table is nearly empty.
The requirement comes from the Postgresql TODO list.
[Benefit]
To find which table is nearly empty and suggest using 'VACUUM FULL' to
release the unused disk
On 4 March 2014 2:41 Euler Taveira wrote:
On 27-02-2014 21:10, Wang, Jing wrote:
Using pg_dump can dump the data into the file with format set to be
'c','t' or plain text. In the existing version the version of server
pg_dump is already there when the format of file is 'c' or 't'. And
even
Enclosed is the patch to implement the requirement that pg_dump should
report version of server pg_dump as comments in the output.
[Benefit]
By running head on pg_dump output, you can readily discover what
version of PostgreSQL was used to generate that dump. Very useful
especially for
Sorry for missing the patch file in the original email. Enclosed please
find it.
Jing Wang
Fujitsu Australia
From: Arulappan, Arul Shaji
Sent: Friday, 28 February 2014 11:21 AM
To: Wang, Jing
Subject: RE: [HACKERS] pg_dump reporing version of server pg_dump as
comments in the output
