OK, noticed how horrible this patch was (thanks for the heads up from
Jaime Casanova). This happens when trying to fetch changes one made on
a test copy after a day of lots of work back to a git repository: you
just make very silly mistakes.
Well, now I got the changes right (tested the patch,
Hi,
I've noticed that db_user_namespace has had the following note
attached to it since 2002:
This feature is intended as a temporary measure until a complete
solution is found. At that time, this option will be removed.
It will be 12 years this year since this temporary measure was
added. I'm
On Sat, Mar 8, 2014 at 6:18 AM, Ishaya Bhatt ishayabh...@gmail.com wrote:
Hi,
I am trying to analyze join performance. But I see that even for a table
having 100,000 rows and join attribute as primary key, postgres always
performs hash join.
Can anyone please tell me under which conditions
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 03/06/2014 10:47 AM, Simon Riggs wrote:
On 5 March 2014 09:28, Simon Riggs si...@2ndquadrant.com wrote:
So that returns us to solving the catalog consistency problem in
pg_dump and similar applications.
No answer, guys, and time is ticking away here.
Sorry, I've accumulated several days
I've found an issue with updatable security barrier views. Locking is
being pushed down into the subquery. Locking is thus applied before
user-supplied quals are, so we potentially lock too many rows.
I'm looking into the code now, but in the mean time, here's a demo of
the problem:
regress=
As mentioned by Pavel also, this patch will be very useful, which provides
below enhancement:
1. Brings consistency between copy from “stdin” and “file”.
2. Consistent with server side copy statement.
3. Also fixes the issue related to “\copy destination file becomes
default
Rajeev rastogi rajeev.rast...@huawei.com writes:
This has been in âReady for committerâ stage for long time.
Yeah, I started to work on it and got distracted, but was working on it
some more yesterday. As submitted, it leaks PGresults, and makes some
inconsistent and mostly undocumented
Dear Hackers --
I'm looking at doing a calculation to determine the number of free buffers
available. A n example ratio that is based on some data structures in
freelist.c as follows:
(StrategyControl-lastFreeBuffer - StrategyControl-firstFreeBuffer) /
(double) NBuffers
Is there a way to get
While registering the service for PostgreSQL on windows, we cannot expect user
to give absolute path always.
So it is required to support relative path as data directory. So this patch
will be very useful to handle the same.
This patch has been in Ready for committer stage for long time.
Please
On Mon, Mar 10, 2014 at 5:58 AM, Wang, Jing ji...@fast.au.fujitsu.com wrote:
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.
[Solution details]
A check function
On Mon, Feb 17, 2014 at 9:17 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Sat, Feb 1, 2014 at 12:31 PM, Amit Kapila amit.kapil...@gmail.com wrote:
I think it's just a very minor coding style thing, so I am marking this
patch as
Ready For Committer.
I could see that this patch has been
Hi Tom, Bruce,
Thank you for your response.
(2014/03/09 2:12), Tom Lane wrote:
Bruce Momjian br...@momjian.us writes:
On Sat, Mar 8, 2014 at 11:31:22AM -0500, Tom Lane wrote:
Tomonari Katsumata t.katsumata1...@gmail.com writes:
[ client_min_messages = info is not documented ]
That's
13 matches
Mail list logo
