details from another thread:
https://www.postgresql.org/message-id/bf2827dcce55594c8d7a8f7ffd3ab77159a9b...@szxeml521-mbs.china.huawei.com
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
mechanism of Hash Join, now there is pipelining Hash
join where probe and build both happens together).
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
r
The result we got was really impressive.
There is a paper by Thomas Neumann on this idea:
http://www.vldb.org/pvldb/vol4/p539-neumann.pdf
Note: VitesseDB has also implemented this approach for Hash Join along with
compilation and their result is really impressive.
Thanks and Regards,
Kumar R
ady this
function takes of handling " NOTICE message that the backend might have sent
just before it died "
Attached is the patch with this change.
Comments?
Thanks and Regards,
Kumar Rajeev Rastogi
dangle-v4.patch
Description: dangle-v4.patch
--
Sent via pgsql-hackers mailing
ssage to client. But with
the current infrastructure, I don’t think there is any way to pass this error
message to client [This error has happened without involvement of the client
side].
Comments?
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
errmsg("terminating connection due to postmaster
>>> shutdown")));
>>
>> Agreed, but I don't think "shutdown" is the right word to use here --
>> that makes it sound like it was orderly. Perhaps "crash"?
>
>Well,
from secure_read and secure_write function will
wait on an additional event as WL_POSTMASTER_DEATH.
2. There is a possibility that the command is read without waiting on latch.
This case is handled by checking postmaster status after command read (i.e.
after ReadCommand).
Attached is the patch.
; On Tue, Oct 13, 2015 at 3:54 PM, Rajeev rastogi
>> <rajeev.rast...@huawei.com>
>> wrote:
>> > If we add the event WL_POSTMASTER_DEATH also, client backend process
>> > handling will become same as other backend process. So postmaster
>> > death can b
On 12th October 2015 20:45, Rajeev Rastogi Wrote:
>>> I observed one strange behavior today that if postmaster process gets
>>> crashed/killed, then it kill all background processes but not the client
>>> backend process.
>> This is a known behavi
e this is not the best solution, we should look for
more appropriate/better one.
Now as it is confirmed to be valid issue, I will spend some time on this to
find if there is something more appropriate solution.
Thanks and Regards,
Kumar Rajeev Rastogi
every command read but it will add extra cost for each query execution.
Any comments?
Thanks and Regards,
Kumar Rajeev Rastogi
and after execution of query. Then comparison of these two dump will be helpful
to further analyze.
Attached is the patch. Please provide your opinion. If it is OK, I will add it
to next commitFest.
Thanks and Regards,
Kumar Rajeev Rastogi
memory_ctxt_dumpv1.patch
Description: memory_ctxt_du
; the
second one is, in my opinion, a key design goal for this feature.
Yes I agree with this. I was in favor of error all the time without involving
deadlock detector.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On 03 August 2015 18:40, Merlin Moncure [mailto:mmonc...@gmail.com] Wrote:
On Sun, Aug 2, 2015 at 11:37 PM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
On 31 July 2015 23:10, Robert Haas Wrote:
I think we're going entirely down the wrong path here. Why is it ever
useful for a backend's lock
continue as it is (or abort
main transaction also??).
Any other suggestion to handle this will be really helpful.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
On 28 July 2015 03:21, Josh Berkus Wrote:
On 07/27/2015 02:47 AM, Rajeev rastogi wrote:
Why have any fixed maximum?
Since we are planning to have nested autonomous transaction, so it is
required to have limit on this so that resources can be controlled.
Is there a particular reason why
.
Thanks, sounds to be a good idea. I shall evaluate the same.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 23 July 2015 21:04, Robert Haas Wrote:
On Thu, Jul 23, 2015 at 1:31 AM, Rajeev rastogi rajeev.rast...@huawei.com
wrote:
2.It should be allowed to deadlock with master transaction. We
need to work-out a solution to avoid deadlock.
This sentence seems to contradict itself. I
.
Requesting for everyone's opinion regarding this based on which we can proceed
to enhance/tune/re-write our design.
Thanks and Regards,
Kumar Rajeev Rastogi
For , =, and = strategies, mark the first scan key
as already matched if scanning in an appropriate direction.
If index tuple contains no nulls we can skip the first
re-check for each tuple.
Author: Kumar Rajeev Rastogi
Committer: Simon Riggs
Thanks and Regards,
Kumar Rajeev Rastogi
will be interested in this or if there were
already any discussion about this in past?
Please provide your opinion/suggestion.
Thanks and Regards,
Kumar Rajeev Rastogi
this issue
has not yet been observed.
Thanks and Regards,
Kumar Rajeev Rastogi
checked version-11 and version-12 and found to be already fixed.
I should have checked the latest version before sending the report…☺
Thanks and Regards,
Kumar Rajeev Rastogi
From: Amit Kapila [mailto:amit.kapil...@gmail.com]
Sent: 25 March 2015 16:00
To: Rajeev rastogi
Cc: Amit Langote; Robert
not sure if we can consider this to be a problem or not but I just wanted
to share as generally it is expected by user to be Materialization faster than
Non-materialized.
Please provide your opinion. If we can do something about this then I can take
up this work.
Thanks and Regards,
Kumar Rajeev
On 23 March 2015 21:39, Robert Haas
On Mon, Mar 23, 2015 at 6:01 AM, Rajeev rastogi
rajeev.rast...@huawei.com wrote:
The cost of re-scan of SeqScan node is considered to be same scan of
SeqScan node, which always assumes that the records is fetched from
disk and hence disk access cost
in many case.
With this change, I did one small performance test on pgbench with prepared
queries for pgbench select with 16 users and observed performance benefit of
10%.
Please provide your opinion?
Thanks and Regards,
Kumar Rajeev Rastogi
. I'll do my best to
improve that, then look to commit this in about 5 hours.
Thanks a lot for support. Please let me know if I also need to add something.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 22 September 2014 18:51, Stephen Frost Wrote:
* Rajeev rastogi (rajeev.rast...@huawei.com) wrote:
Thanks, I shall start to prepare a patch for this optimization and share in 1
or 2 days.
This sounded interesting to me also- please be sure to put it on the open
commitfest once you have
On 24 September 2014 17:15, Michael Paquier Wrote:
On Wed, Sep 24, 2014 at 7:59 PM, Abhijit Menon-Sen a...@2ndquadrant.com
wrote:
I can never remember that pg_controldata takes only a dirname rather
than -D dirname, and I gather I'm not the only one. Here's a tiny
patch to make it work
On 22 September 2014 19:17, Heikki Linnakangas wrote:
On 09/22/2014 04:45 PM, Tom Lane wrote:
Heikki Linnakangas hlinnakan...@vmware.com writes:
On 09/22/2014 07:47 AM, Rajeev rastogi wrote:
So my proposal is to skip the condition check on the first scan key
condition for every tuple
where the optimization doesn't help.
Thanks, I shall start to prepare a patch for this optimization and share in 1
or 2 days.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
the patch for this improvement.
Please provide your feedback. Also let me know if I am missing something.
Thanks and Regards,
Kumar Rajeev Rastogi
--Schema
create table tbl2(id1 int, id2 varchar(10), id3 int);
create index idx2 on tbl2(id2, id3);
--Procedure to insert 1M data:
create or replace
of the first synchronous-standby-num standby
fails.
Let me know incase if something is not clear.
Thanks and Regards,
Kumar Rajeev Rastogi.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. In case of processing of CREATE TABLESPACE redo, same is
already handled.
I will add this to 2014-08 CF for review.
Thanks and Regards,
Kumar Rajeev Rastogi
rec_issue_with_drop_tblspc_redo.patch
Description: rec_issue_with_drop_tblspc_redo.patch
--
Sent via pgsql-hackers mailing list (pgsql
to degrade the synchronous
level of master, if all synchronous standbys are down.
I plan to resubmit this with better design sometime in 9.5.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 01 July 2014 12:00, Amit Kapila Wrote:
On Tue, Jul 1, 2014 at 11:46 AM, Rajeev rastogi
rajeev.rast...@huawei.commailto:rajeev.rast...@huawei.com wrote:
On 30 June 2014 22:50, Pavel Stehule Wrote:
I didn't find a related message.
?
I think there have been some confusion, the design idea
to datum, which will lead to crash.
I have done testing to verify this on win32 and able to observe the crash where
as it works fine on Linux.
Also can we change the description of function pg_buffercache_pages to
include pinning_backend also in the description.
Thanks and Regards,
Kumar Rajeev
missing something.
Thanks and Regards,
Kumar Rajeev Rastogi
Rajeev Rastogi
git master
* includes necessary docs
* I think It is very good and necessary feature.
If Kumar Rajeev Rastogi do not have any extra comments, then I think patch is
ready for committer.
I have reviewed this patch. Please find my review comments below:
1. Command start-up option (e.g
. If no objection from others, we can go ahead
with the current prefixing approach.
Thanks and Regards,
Kumar Rajeev Rastogi
-up in pg_clog.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 12 May 2014 19:27, Heikki Linnakangas Wrote:
On 01/24/2014 02:10 PM, Rajeev rastogi wrote:
We are also planning to implement CSN based snapshot.
So I am curious to know whether any further development is happening
on this.
I started looking into this, and plan to work on this for 9.5
and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
have to print other time (i.e. parsing + analyzing +
rewrite), then IMHO
we can print with some different name instead of including in Planning time
only.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
share your design (even rough is OK), I will see if I
can contribute to that in some-way.
Thanks and Regards,
Kumar Rajeev Rastogi
conflict between them,
I am distinguishing at this level.
Please correct me If I am wrong anywhere and also please provide your thought
on this and on overall design.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
/AtATEOX kind of
routines in WIP patch.
Comments/feedbacks/doubts are welcome.
Thanks and Regards,
Kumar Rajeev Rastogi
/AtATEOX kind of
routines in WIP patch.
Comments/feedbacks/doubts are welcome.
Thanks and Regards,
Kumar Rajeev Rastogi
Rajeev Rastogi
: 109
Snapshot-xip[]: 100, 101, 102, 103, 105, 106
Snapshot-subxip[]: 104
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers
transaction, it is automatically taken care.
Any comment/feedback/doubt are welcome?
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
sent, I have done basic testing and it works fine.
Any comments?
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
am not planning to support only using plpgsql. Initially
we can support this
Using the standalone SQL-commands and then later we can enhance based on this
infrastructure
to be used using plpgsql, triggers.
Thanks and Regards,
Kumar Rajeev Rastogi
to iterative count(*), which might degrade performance for VACUUM.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 05 April 2014 04:14, Tom Lane
[ pgctl_win32service_rel_dbpath_v6.patch ]
Committed with minor corrections, mostly but not all cosmetic.
Thanks a lot...
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
the attached patch with the fix.
Thanks and Regards,
Kumar Rajeev Rastogi
multiconstissuev1.patch
Description: multiconstissuev1.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 27 March 2014 17:16, Tom Lane Wrote:
I agree we need to make the docs match the code, but changing behavior
that's been like that for ten or fifteen years isn't the answer.
Sounds good.
Please find the attached patch with only documentation change.
Thanks and Regards,
Kumar Rajeev Rastogi
code change. After modification, result will be as follows:
postgres=# create database newtempdb template postgres;
ERROR: DB name postgres given as template is not a template database
Please provide your feedback.
Thanks and Regards,
Kumar Rajeev Rastogi
datistemplate_issue.patch
max_connection value.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
changed in standby also (if you have not taken back
again)?
Let me know If I have missed something.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
earlier.
I have modified the corresponding documentation.
Please find the attached revised patch.
Thanks and Regards,
Kumar Rajeev Rastogi
psql-copy-count-tag-20140313.patch
Description: psql-copy-count-tag-20140313.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
they will be effected with
additional status result).
To me option #1 seems to be more suitable specially since there is an option to
disable
the status output by giving -q.
Please provide your opinion or let me know If I have missed something.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql
of COPY TO STDOUT, if we don't print anything, then user does not
have any direct way of finding
that how many rows were copied from table to STDOUT, which might have been very
useful.
Please let me know your opinion or if I have missed something.
Thanks and Regards,
Kumar Rajeev Rastogi
destination file for next command given in sequence”.
This has been in “Ready for committer” stage for long time.
Please check if this can be committed now or any other changes required.
Thanks and Regards,
Kumar Rajeev Rastogi
check if this can be committed now or any other changes required.
Thanks and Regards,
Kumar Rajeev Rastogi
-Original Message-
From: MauMau [mailto:maumau...@gmail.com]
Sent: 24 February 2014 15:31
To: Rajeev rastogi
Cc: pgsql-hackers@postgresql.org; Magnus Hagander
Subject: Re
this as Ready for Committer.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
*
* ...existing function descripton
*/
Added.
(2)
Add errno description as in:
fprintf(stderr, _(could not get current working directory: %s\n,
strerror(errno)));
Modified.
Please find the attached modified patch.
Thanks and Regards,
Kumar Rajeev Rastogi
your suggestion.
Now only one version of make_absolute_path there defined in src/port/path.c
Found one small memory leak in the existing function
make_absolute_path(miscinit.c),
fixed the same.
Please find the revised patch.
Thanks and Regards,
Kumar Rajeev Rastogi
On 12 February 2014 12:16, KONDO Mitsumasa Wrote:
Hi Rajeev,
(2014/01/29 17:31), Rajeev rastogi wrote:
No Issue, you can share me the test cases, I will take the
performance report.
Attached patch is supported to latest pg_stat_statements. It includes
min, max, and stdev statistics
changes messages to the
following:
Process holding the lock: A. Wait queue: B.
Processes holding the lock: A, B. Wait queue: C.
This looks good to me also.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
me know
of that. Then, I'll change the patch status to ready for committer.
I will update commitFest with the latest patch immediately after sending the
mail.
Thanks and Regards,
Kumar Rajeev Rastogi
pgctl_win32service_rel_dbpath_v4.patch
Description: pgctl_win32service_rel_dbpath_v4.patch
find the attached revised patch.
Thanks and Regards,
Kumar Rajeev Rastogi
pgctl_win32service_rel_dbpath_v3.patch
Description: pgctl_win32service_rel_dbpath_v3.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
...@lab.ntt.co.jp
mailto:kondo.mitsum...@lab.ntt.co.jp wrote:
Rebased patch is attached.
Does this fix the Windows bug reported by Kumar on
20/11/2013 ?
Sorry, I was misunderstanding. First name of Mr. Rajeev Rastogi is
Kumar! I searched only e-mail address
:
'=' : incompatible types - from 'LWLockPadded *' to 'LWLock *'
1.\src\backend\postmaster\postmaster.c(5856) : warning C4133: '=' :
incompatible types - from 'LWLock *' to 'LWLockPadded *'
Attached is the patch with the fix.
Thanks and Regards,
Kumar Rajeev Rastogi
compile_issue_lwlock.patch
Description
this as Ready for Committer.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and Regards,
Kumar Rajeev Rastogi
unwanted_prototype.patch
Description: unwanted_prototype.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
...@lab.ntt.co.jp
mailto:kondo.mitsum...@lab.ntt.co.jp wrote:
Rebased patch is attached.
Does this fix the Windows bug reported by Kumar on 20/11/2013 ?
Sorry, I was misunderstanding. First name of Mr. Rajeev Rastogi is
Kumar! I searched only e-mail address and title
a synchronous
transaction and we are in degraded mode.
5. Please add more if I am missing something.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
?
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a security standpoint that's not such a wise idea, and
errdetail_log() is what should be used.
Fixed. I added an errdetail_log_plural() for this, too.
I think you have attached wrong patch.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers
and
Which process is already in queue.
2. Can we give a better name to new variable 'buf1'?
3. Do we need to take performance reading to see if any impact?
4. Do we require documentation?
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers
changes for the same.
I have attached the changed patch. Please provide your further feedback, if any.
Thanks and Regards,
Kumar Rajeev Rastogi
pgctl_win32service_rel_dbpath_v2.patch
Description: pgctl_win32service_rel_dbpath_v2.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers
,
then
it should be able to handle this command even though sync
replica is
not available.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
SQL-callable functions as Heikki
suggested to degrade instead of auto-degrade then user can handle at-least some
of the above scenarios if not all based on their experience and observation.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers
. enable_async_master
2. sync_standalone_master
3. enable_nowait_master
4. enable_nowait_resp_master
Please provide your suggestion on above name or any other?.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
file.
Attached is the patch with the fix.
Please provide your opinion.
I will add this to Jan 2014 CommitFest.
Thanks and Regards,
Kumar Rajeev Rastogi
pgctl_win32service_rel_dbpath.patch
Description: pgctl_win32service_rel_dbpath.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On 12 December 2013, Heikki Linnakangas 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 changes are okay.
Changes are fine. Thanks you.
I have uploaded the
On 12th December 2013, Rajeev Rastogi Wrote:
On 9th December, Amit Khandelkar wrote:
1. slashcopyissuev1.patch :- This patch fixes the \COPY issue.
You have removed the if condition in this statement, mentioning that it is
always true now:
- if (copystream
already mentions
that COPY should show the COUNT tag, and does not mention anything specific to
client-side COPY.
OK.
Please provide you opinion, based on which I shall prepare new patch and share
the same.
Thanks and Regards,
Kumar Rajeev Rastogi
the attached two separate patches:
1. slashcopyissuev1.patch :- This patch fixes the \COPY issue.
2. initialcopyissuev1_ontopofslashcopy.patch : Fix for COPY table FROM
STDIN/STDOUT doesn't show count tag.
Thanks and Regards,
Kumar Rajeev Rastogi
slashcopyissuev1.patch
Description
.
Kindly check once whether changes are okay.
Changes are fine. Thanks you.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
patch in CF app and marked it as Ready For
Committer.
Thanks a lot.
Thanks and Regards,
Kumar Rajeev Rastogi
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 27 November 2013, Naoya Anzai wrote:
Hi, Rajeev
I tested the latest patch. My observation is:
If we give relative data directory path while registering the
service, then service start fails.
But same works if the data directory is absolute path.
Looks like an existing
provide your opinion.
Thanks and Regards,
Kumar Rajeev Rastogi
pg_resetxlogsectionV4.patch
Description: pg_resetxlogsectionV4.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and Regards,
Kumar Rajeev Rastogi
pg_resetxlogsectionV3.patch
Description: pg_resetxlogsectionV3.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 25 November 2013, Rajeev Rastogi Wrote:
One suggestion:
Instead of using sizeof(cmdLine),
a. Can't we use strlen (hence small 'for' loop).
b. Or use memmove to move one byte.
I looked at this patch a bit. I agree that we need to fix
pgwin32_CommandLine to double-quote
1 - 100 of 117 matches
Mail list logo
