On Fri, Oct 11, 2013 at 10:36 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-10-11 09:22:50 +0530, Amit Kapila wrote:
I think it will be difficult to prove by using any compression
algorithm, that it compresses in most of the scenario's.
In many cases it can so happen that the WAL
On Thu, Oct 10, 2013 at 3:17 AM, Gibheer gibh...@zero-knowledge.org wrote:
On Mon, 7 Oct 2013 11:39:55 +0530
Amit Kapila amit.kapil...@gmail.com wrote:
Robert Haas wrote:
On Mon, Aug 5, 2013 at 2:04 AM, Andres Freund
andres(at)2ndquadrant(dot)com wrote:
Hmm. It seems like this match
by a ResourceOwner
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sun, Oct 13, 2013 at 2:08 PM, Gibheer gibh...@zero-knowledge.org wrote:
On Sun, 13 Oct 2013 11:38:17 +0530
Amit Kapila amit.kapil...@gmail.com wrote:
On Thu, Oct 10, 2013 at 3:17 AM, Gibheer gibh...@zero-knowledge.org
wrote:
On Mon, 7 Oct 2013 11:39:55 +0530
Amit Kapila amit.kapil
On Mon, Oct 14, 2013 at 5:11 PM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Oct 13, 2013 at 3:07 AM, Amit Kapila amit.kapil...@gmail.com wrote:
1. Do you think we should add information about pg_dynshmem file at link:
http://www.postgresql.org/docs/devel/static/storage-file-layout.html
On Mon, Oct 14, 2013 at 8:40 PM, Magnus Hagander mag...@hagander.net wrote:
On Mon, Oct 14, 2013 at 2:28 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Oct 10, 2013 at 9:34 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On further analysis, I found that hang occurs in some of Windows
API
.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
such entities which need connection.
Also we might need to have different infrastructure in code to make
these options available to users.
I think having different parameters to configure maximum connections
for different entities can complicate both code as well as user's job.
With Regards,
Amit Kapila
On Tue, Oct 15, 2013 at 6:30 AM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/10/13 0:14), Amit Kapila wrote:
On Fri, Oct 11, 2013 at 10:36 PM, Andres Freund and...@2ndquadrant.com
wrote:
But maybe pglz is just not a good fit for this, it really
isn't a very good algorithm
{} while (0)
#endif
I think rather than having writing code like above at places where
va_copy is used, we can use something like:
#ifdef WIN32
#define va_copy(dest, src) (dest = src)
#endif
and define HAVE_VA_COPY to 1 for non-windows platform.
With Regards,
Amit Kapila.
EnterpriseDB: http
On Mon, Oct 14, 2013 at 11:00 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Oct 10, 2013 at 9:34 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On further analysis, I found that hang occurs in some of Windows
API(FindFirstFile, RemoveDirectroy) when
/
Long path is much less than 260 char limit on windows, I have
observed this problem with path length 130 (approx.)
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
long_path.rar
Description: application/rar
--
Sent
On Wed, Oct 16, 2013 at 2:04 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Oct 15, 2013 at 4:14 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Tue, Oct 15, 2013 at 6:28 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Oct 15, 2013 at 2:55 PM, Robert Haas robertmh...@gmail.com
On Wed, Oct 16, 2013 at 4:30 AM, Gibheer gibh...@zero-knowledge.org wrote:
On Mon, 14 Oct 2013 11:52:57 +0530
Amit Kapila amit.kapil...@gmail.com wrote:
On Sun, Oct 13, 2013 at 2:08 PM, Gibheer gibh...@zero-knowledge.org
wrote:
On Sun, 13 Oct 2013 11:38:17 +0530
Amit Kapila amit.kapil
mystat_sequence is missing, although it
doesn't seem to be necessary, but if you can provide the definition
you are using
then it will be better.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
, the error 'tuple concurrently updated' appears...
Needless to say, that it disappears too... unpredictably.
Sometimes, it can shows up contisnously.
Do you see any other problem due to this error in your database?
Tell me if you need some more detailed information.
Stephan
With Regards,
Amit
On Fri, Oct 18, 2013 at 9:01 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Oct 9, 2013 at 2:28 PM, Robert Haas robertmh...@gmail.com wrote:
On Sat, Sep 14, 2013 at 3:03 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Monday, July 08, 2013 5:16 PM Andres Freund wrote:
On 2013-07-08 17:10
existing LSNs,
with options to 1) report only the highest one in a given file, 2)
report only those that exceed some threshold. So maybe pg_reportlsn or
pg_extractlsn.
How about extending it validate database in more meaningful way and
name it as validatedb.
With Regards,
Amit Kapila.
EnterpriseDB
On Tue, Oct 15, 2013 at 11:41 AM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/10/15 13:33), Amit Kapila wrote:
Snappy is good mainly for un-compressible data, see the link below:
http://www.postgresql.org/message-id/CAAZKuFZCOCHsswQM60ioDO_hk12tA7OG3YcJA8v=4yebmoa
On Thu, Oct 17, 2013 at 8:57 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Wed, Oct 16, 2013 at 4:30 AM, Gibheer gibh...@zero-knowledge.org wrote:
On Mon, 14 Oct 2013 11:52:57 +0530
Amit Kapila amit.kapil...@gmail.com wrote:
On Sun, Oct 13, 2013 at 2:08 PM, Gibheer gibh...@zero
On Sun, Oct 20, 2013 at 1:26 AM, Gibheer gibh...@zero-knowledge.org wrote:
On Sat, 19 Oct 2013 12:09:57 +0530
Amit Kapila amit.kapil...@gmail.com wrote:
On Thu, Oct 17, 2013 at 8:57 AM, Amit Kapila
amit.kapil...@gmail.com wrote:
On Wed, Oct 16, 2013 at 4:30 AM, Gibheer
gibh...@zero
to me is for VACUUM to estimate the number of remaining
dead tuples somehow and send that in its message.).
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Mon, Oct 21, 2013 at 4:40 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/10/19 14:58), Amit Kapila wrote:
On Tue, Oct 15, 2013 at 11:41 AM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
In general, my thinking is that we should prefer compression to reduce
IO (WAL
On Tue, Oct 22, 2013 at 9:22 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Oct 22, 2013 at 12:47 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Mon, Oct 21, 2013 at 4:40 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/10/19 14:58), Amit Kapila wrote:
On Tue, Oct 15
On Mon, Oct 21, 2013 at 10:54 AM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 20 October 2013 12:06 Amit Kapila wrote:
On Tue, Oct 15, 2013 at 3:37 PM, Haribabu kommi haribabu.ko...@huawei.com
wrote:
On 12 October 2013 11:30 Tom Lane wrote:
Haribabu kommi haribabu.ko...@huawei.com writes
On Wed, Oct 23, 2013 at 7:05 AM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote:
(2013/10/22 12:52), Fujii Masao wrote:
On Tue, Oct 22, 2013 at 12:47 PM, Amit Kapila amit.kapil...@gmail.com
wrote:
On Mon, Oct 21, 2013 at 4:40 PM, KONDO Mitsumasa
kondo.mitsum...@lab.ntt.co.jp wrote
this syntax.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
cluster_index_specification
{
ClusterStmt *n = makeNode(ClusterStmt);
- n-relation = $3;
- n-indexname = $4;
- n-verbose = $2;
+ n-relation = $4;
+ n-freeze_min_age = $2 ? 0 : -1;
+ n-indexname = $5;
+ n-verbose = $3;
..
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent
and performance and call it done, but I think giving at
least an option to user to make compression altogether off should be
still considered.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Thu, Oct 24, 2013 at 10:39 PM, Josh Berkus j...@agliodbs.com wrote:
On 10/23/2013 09:58 PM, Amit Kapila wrote:
I wonder why anyone would like to freeze during CLUSTER command when
they already have separate way (VACUUM FREEZE) to achieve it, do you
know or can think of any case where user
On Fri, Oct 25, 2013 at 4:29 AM, Thomas Munro mu...@ip9.org wrote:
On 24 October 2013 05:58, Amit Kapila amit.kapil...@gmail.com wrote:
On Thu, Oct 24, 2013 at 4:58 AM, Thomas Munro mu...@ip9.org wrote:
Hi
I noticed that CLUSTER doesn't have a FREEZE option. Here is a patch to
add
there will be many more things at top level which might be
required to generalize LIKE operator optimisation, but I could think
of only above as per my initial look at this problem. I think more
thoughts/suggestions on this problem can help someone to attempt a
patch for this problem.
With Regards,
Amit
On Mon, Oct 28, 2013 at 3:22 PM, Stéphan BEUZE
stephan.be...@douane.finances.gouv.fr wrote:
Le 19/10/2013 05:21, Amit Kapila a écrit :
On Fri, Oct 18, 2013 at 3:43 PM, Stéphan BEUZE
stephan.be...@douane.finances.gouv.fr wrote:
* CONTEXT
Two Java threads are created. One is connected
RecordTransactionCommit() should take care of doing it.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
, which is changed
by commit d2aecae, so we need to change that calculation as well.
Please find the attached patch to fix this problem.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
bug_size_calc_dsm_win.patch
Description: Binary data
--
Sent via pgsql-hackers mailing
On Wed, Oct 16, 2013 at 1:44 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Tue, Oct 15, 2013 at 6:28 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Oct 15, 2013 at 2:55 PM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Oct 14, 2013 at 1:30 PM, Tom Lane t...@sss.pgh.pa.us wrote
to post to pgsql-bugs again.
I could also reproduce this issue. The situation is very rare such
that an exe with name same as first part of directory should exist
in installation path.
I suggest you can post your patch in next commit fest.
With Regards,
Amit Kapila.
EnterpriseDB: http
the loop.
Although savings are small considering this doesn't occur in any
performance path, still I think this is right thing to do in code.
It is better to register this patch in CF app list, unless someone
feels this is not right.
With Regards,
Amit Kapila.
EnterpriseDB: http
On Fri, Nov 1, 2013 at 9:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
On Thu, Oct 31, 2013 at 2:41 AM, Gurjeet Singh gurj...@singh.im wrote:
Just a small patch; hopefully useful.
This is valid saving as we are filling array ListenSocket
/message-id/6C0B27F7206C9E4CA54AE035729E9C382853263C@szxeml509-mbs
If this is the right thing, I can rebase the patch and make it ready.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Tue, Nov 5, 2013 at 12:52 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
On Mon, Nov 4, 2013 at 8:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Really I'd like to see standalone mode, in its current form, go away
completely. I had a prototype patch
though chances of
hitting such problem is less.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Oct 22, 2013 at 2:09 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 22 October 2013 10:15 Amit Kapila wrote:
On Mon, Oct 21, 2013 at 10:54 AM, Haribabu kommi haribabu.ko...@huawei.com
wrote:
Actually what I had in mind was to use nkeep to estimate n_dead_tuples
similar to how
after reset:\n\n));
Even after first if check fails, still you continue to check other
values, it is better if you can have check if (changedParam) before
calling this function
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql
On Fri, Nov 8, 2013 at 10:56 AM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 07 November 2013 09:42 Amit Kapila wrote:
I am not sure whether the same calculation as done for new_rel_tuples
works for new_dead_tuples, you can once check it.
I didn't find any way to calculate
else have thoughts about how can we display values which can make
current situation better for user.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
or provide suggestions, else you can make a
combined patch of this and other warning you saw on windows and upload
to next CF so that it doesn't get lost.
I checked that you have already submitted a patch for this warning
alone in CF.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
On Sat, Nov 9, 2013 at 1:00 PM, David Rowley dgrowle...@gmail.com wrote:
On Sat, Nov 9, 2013 at 7:29 PM, Amit Kapila amit.kapil...@gmail.com wrote:
Thanks for the link.
The reason that we don't see more warnings for this is that it seems in all
other places where we have used
On Sat, Nov 9, 2013 at 2:43 AM, Noah Misch n...@leadboat.com wrote:
On Wed, Nov 06, 2013 at 10:14:53AM +0530, Amit Kapila wrote:
On Thu, Oct 31, 2013 at 8:22 PM, Noah Misch n...@leadboat.com wrote:
About unclean FATAL-then-ERROR scenario, one way to deal at high level
could be to treat
Hi Naoya,
On Thu, Oct 31, 2013 at 5:42 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Oct 31, 2013 at 1:44 AM, Asif Naeem anaeem...@gmail.com wrote:
On Thu, Oct 31, 2013 at 10:17 AM, Amit Kapila amit.kapil...@gmail.com
wrote:
On Tue, Oct 29, 2013 at 12:46 PM, Naoya Anzai
anzai-na
On Mon, Nov 11, 2013 at 3:14 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 08 November 2013 18:35 Amit Kapila wrote:
On Fri, Nov 8, 2013 at 10:56 AM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 07 November 2013 09:42 Amit Kapila wrote:
I am not sure whether the same
On Tue, Nov 12, 2013 at 9:37 PM, Bruce Momjian br...@momjian.us wrote:
On Wed, Oct 23, 2013 at 10:31:39AM +0530, Amit Kapila wrote:
On Tue, Oct 22, 2013 at 3:04 AM, Piotr Marcinczyk pmarc...@gmail.com wrote:
Hi,
I would like to implement item from TODO marked as easy: Add \i option
On Wed, Nov 13, 2013 at 4:05 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 01 October 2013 00:56 Amit Kapila wrote:
On Mon, Sep 30, 2013 at 9:07 PM, Peter Eisentraut pete...@gmx.net
wrote:
On 9/28/13 3:05 AM, Amit Kapila wrote:
Now as we have an agreement, I had updated patch
warning.
d. removed trailing white spaces.
e. update PQconninfoOptions array to include offset.
Any objections for adding this idea/patch to CF?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
standalone_backend.3.patch
Description: Binary data
--
Sent via pgsql-hackers
On Wed, Nov 13, 2013 at 7:23 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Wed, Nov 13, 2013 at 4:05 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 01 October 2013 00:56 Amit Kapila wrote:
On Mon, Sep 30, 2013 at 9:07 PM, Peter Eisentraut pete...@gmx.net
wrote:
On 9/28/13 3:05
On Wed, Nov 13, 2013 at 12:02 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 12 November 2013 08:47 Amit Kapila wrote:
On Mon, Nov 11, 2013 at 3:14 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 08 November 2013 18:35 Amit Kapila wrote:
On Fri, Nov 8, 2013 at 10:56 AM
On Fri, Nov 15, 2013 at 10:18 PM, Peter Eisentraut pete...@gmx.net wrote:
On 11/14/13, 2:50 AM, Amit Kapila wrote:
Find the rebased version attached with this mail.
Doesn't build:
openjade -wall -wno-unused-param -wno-empty -wfully-tagged -D . -D . -c
/usr/share/sgml/docbook/stylesheet
On Sat, Nov 16, 2013 at 4:35 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 16 November 2013 09:43 Amit Kapila wrote:
On Fri, Nov 15, 2013 at 10:18 PM, Peter Eisentraut pete...@gmx.net
wrote:
On 11/14/13, 2:50 AM, Amit Kapila wrote:
Find the rebased version attached with this mail
On Fri, Nov 15, 2013 at 5:21 PM, Simon Riggs si...@2ndquadrant.com wrote:
On 14 November 2013 03:41, Amit Kapila amit.kapil...@gmail.com wrote:
I have gone through the mail chain of this thread and tried to find
the different concerns or open ends for this patch.
Not enough. This feature
might need to narrow
down the problem by having less number of queries in your JDBC
application. If possible start by having only 1 or 2 queries and then
see how many times parse,bind,execute gets called.
The OS is CentOS 5. The PG is 9.0.9. The JDBC is 9.2.
With Regards,
Amit
is same in switch case or while get
opt_long() function call. I think this makes code easy to understand
and modify.
However there is no functionality issue here, so you can keep the code
as per your existing patch as well, this is just a suggestion.
With Regards,
Amit Kapila.
EnterpriseDB: http
On Mon, Nov 18, 2013 at 6:28 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 17 November 2013 12:25 Amit Kapila wrote:
On Sat, Nov 16, 2013 at 4:35 PM, Haribabu kommi
Find the rebased version attached with this mail.
ereport(ERROR,
(errcode
search but didn't find PostgreSQL had similar join hints except
for enable_* setting which doesn't help in my case.
PostgreSQL doesn't have join hints.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Mon, Nov 18, 2013 at 8:31 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 18 November 2013 20:01 Amit Kapila wrote:
Code changes are fine.
If two or three errors are present in the configuration file, it
prints the last error
Configuration parameter file only. Is it required
On Fri, Nov 15, 2013 at 10:52 AM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 15 November 2013 10:00 Amit Kapila wrote:
On Wed, Nov 13, 2013 at 12:02 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
With the simulated bloat test run for 1 hour the bloat occurred as
below
On Tue, Nov 19, 2013 at 2:06 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 19 November 2013 09:59 Amit Kapila wrote:
On Mon, Nov 18, 2013 at 8:31 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 18 November 2013 20:01 Amit Kapila wrote:
Code changes are fine.
If two
On Wed, Nov 20, 2013 at 2:05 AM, Christopher Browne cbbro...@gmail.com wrote:
On Mon, Nov 18, 2013 at 1:01 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Sat, Nov 16, 2013 at 4:57 AM, Christopher Browne cbbro...@gmail.com
wrote:
I picked the location of the 'g:' in the opt_long() call
'standalone_datadir' (which is already in
patch) a good candidate for special switch?
How does having one more new switch helps better?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
functions or mimic some handling done at other
place, then it is worth trying.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
this error on latest code.
I think you need to regenerate preproc.y by using command perl
mkvcbuild.pl before build.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On Thu, Nov 21, 2013 at 8:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
Here what I have in mind is that:
a. In pg_dump or other internal utilities where we want to use this
feature, they should call PQenableStart() or some other API before
calling
On Thu, Nov 21, 2013 at 9:11 AM, Amit Kapila amit.kapil...@gmail.com wrote:
On Thu, Nov 21, 2013 at 2:14 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
The argument elsewhere in this thread was that the reason for putting
this in the connection options was so
, but for now I have
prepared patch with approach a), as I could not see any problem with
it.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
pvsnprintf_issue.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
and then
interpolate the variable's value as a quoted string:
testdb= \set content `cat my_file.txt`
testdb= INSERT INTO my_table VALUES (:'content');
or do you prefer an alternative without any kind of quote using \ib?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql
On Thu, Nov 21, 2013 at 9:54 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Thu, Nov 21, 2013 at 8:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
Here what I have in mind is that:
Why would you make psql behave differently from our other command-line
On Fri, Nov 22, 2013 at 9:30 AM, Amit Kapila amit.kapil...@gmail.com wrote:
In master branch, server is not getting started with log level as debug5.
Simple steps to reproduce the problem:
a. initdb -D ..\..\Data
b. change log_min_messages = debug5 in postgresql.conf
c. start server (pg_ctl
On Sun, Nov 24, 2013 at 4:36 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
On Fri, Nov 22, 2013 at 9:30 AM, Amit Kapila amit.kapil...@gmail.com wrote:
Again looking at it, I think better fix would be to restore 'errno'
from 'edata-saved_errno' in errfinish
On Sun, Nov 24, 2013 at 10:22 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Amit Kapila amit.kapil...@gmail.com writes:
I think that still this kind of problems can be there at other
places in code. I checked few places and suspecting secure_read() can
also have similar problem:
case
On Fri, Nov 22, 2013 at 12:12 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 19 November 2013 10:33 Amit Kapila wrote:
If I understood correctly, then your patch's main intention is to
correct the estimate of dead tuples, so that it can lead to Vacuum
cleaning the table/index which
On Mon, Nov 25, 2013 at 9:17 AM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
On Sat, Nov 9, 2013, Amit Kapila wrote
Further Review of this patch:
a. there are lot of trailing whitespaces in patch.
b. why to display 'First log segment after reset' in 'Currrent
pg_control values' section
if this number is not right in some cases.
d. forget about this optimization and reject the patch.
I think by doing option 'b' and 'c' together can make this
optimization usable in cases where it is actually useful.
Opinions/Suggestions?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
On Wed, Nov 27, 2013 at 7:35 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Nov 27, 2013 at 12:56 AM, Amit Kapila amit.kapil...@gmail.com wrote:
The basic idea is that you use a rolling hash function to divide up
the history data into chunks of a given average size. So we scan
On Tue, Nov 26, 2013 at 5:33 PM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
On 26 November 2013, Amit Kapila Wrote:
Further Review of this patch:
b. why to display 'First log segment after reset' in 'Currrent
pg_control values' section as now the same information
is available in new
On Thu, Nov 28, 2013 at 12:11 PM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
On 28 November 2013, Amit Kapila Wrote:
Further Review of this patch:
b. why to display 'First log segment after reset' in 'Currrent
pg_control values' section as now the same information
is available
On Tue, Nov 26, 2013 at 7:26 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 25 November 2013 10:43 Amit Kapila wrote:
On Fri, Nov 22, 2013 at 12:12 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 19 November 2013 10:33 Amit Kapila wrote:
If I understood correctly, then your
On Fri, Nov 29, 2013 at 10:00 AM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
On 29 November 2013, Amit Kapila Wrote:
Further Review of this patch:
I have done few more cosmetic changes in your patch, please find the
updated patch attached with this mail.
Kindly check once whether
On Mon, Dec 2, 2013 at 7:40 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 29 November 2013 03:05 Robert Haas wrote:
On Wed, Nov 27, 2013 at 9:31 AM, Amit Kapila amit.kapil...@gmail.com
wrote:
I tried modifying the existing patch to support the dynamic rollup as follows.
For every 32
to see simple queries
scaling as per your expectation, you
can try with complex one's.
Note - post this on pgsql-performance as well.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Thu, Dec 5, 2013 at 7:25 AM, Peter Eisentraut pete...@gmx.net wrote:
On Thu, 2013-11-14 at 12:11 +0530, Amit Kapila wrote:
If an application wants to allow these connection parameters to be
used, it would need to do PQenableStartServer() first. If it doesn't,
those connection parameters
On Wed, Dec 4, 2013 at 10:40 AM, Claudio Freire klaussfre...@gmail.com wrote:
On Wed, Dec 4, 2013 at 12:57 AM, Amit Kapila amit.kapil...@gmail.com wrote:
As a quick side, we also repeated the same experiment on an EC2 instance
with 16 CPU cores, and found that the scale out behavior became
is fixed, so may be auto tuning it
based on some parameter's can
help such situations.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
been discussed previously to resolve it and it doesn't seem to be
a good way to handle it. Please refer link:
http://www.postgresql.org/message-id/1339601668-sup-4...@alvh.no-ip.org
You can go through that mail chain and see if there can be a better
solution than Approach-2.
With Regards,
Amit
On Fri, Nov 29, 2013 at 6:55 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 29 November 2013 12:00 Amit Kapila wrote:
On Tue, Nov 26, 2013 at 7:26 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
Few questions about your latest patch:
a. Is there any reason why you are doing
On Fri, Dec 6, 2013 at 12:10 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 05 December 2013 21:16 Amit Kapila wrote:
Note -
a. Performance is data is taken on my laptop, needs to be tested on
some better m/c b. Attached Patch is just a prototype of chunkwise
concept, code needs
but the calculation for analyse (like sort)
will make it costly.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Dec 6, 2013 at 3:39 PM, Haribabu kommi
haribabu.ko...@huawei.com wrote:
On 06 December 2013 12:29 Amit Kapila wrote:
Note -
a. Performance is data is taken on my laptop, needs to be tested on
some better m/c b. Attached Patch is just a prototype of chunkwise
concept, code needs
On Thu, Dec 5, 2013 at 6:30 PM, MauMau maumau...@gmail.com wrote:
From: Amit Kapila amit.kapil...@gmail.com
On Wed, Dec 4, 2013 at 7:57 PM, MauMau maumau...@gmail.com wrote:
Approach-2 has been discussed previously to resolve it and it doesn't seem
to be
a good way to handle it. Please
On Sat, Dec 7, 2013 at 6:02 PM, MauMau maumau...@gmail.com wrote:
From: Amit Kapila amit.kapil...@gmail.com
Today, I had again gone through all the discussion that happened at
that time related to this problem
and I found that later in discussion it was discussed something on
lines as your
and this utility?
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
701 - 800 of 3337 matches
Mail list logo
