Re: [HACKERS] [PATCH] SQL function to report log message

Hi All, On Tue, Nov 17, 2015 at 12:10 PM, Peter Eisentraut wrote: > On 11/17/15 2:16 AM, Jim Nasby wrote: > > On 11/15/15 10:56 PM, dinesh kumar wrote: > >> So, shall we make this pg_report_log TO pg_write_log OR pg_ereport OR > >> from you. > > > > W

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Tue, Nov 17, 2015 at 1:02 AM, Michael Paquier wrote: > On Mon, Nov 16, 2015 at 11:27 AM, Michael Paquier wrote: > > In short, it seems that this patch is better rejected. And I am > > planning to do so if there are no complaints. > > OK, done so in the CF app. > Dinesh, please do not be discou

Re: [HACKERS] [PATCH] SQL function to report log message

On Mon, Nov 16, 2015 at 3:58 PM, Kevin Grittner wrote: > On Sunday, November 15, 2015 8:51 PM, Craig Ringer > wrote: > > > I'd prefer to omit fields if explicitly assigned to NULL. You can > > always use coalesce if you want the string 'NULL'; I agree with > > others here that the vast majority

Re: [HACKERS] [PATCH] SQL function to report log message

Hi, On Mon, Nov 16, 2015 at 2:50 AM, Peter Eisentraut wrote: > On 10/22/15 3:20 AM, dinesh kumar wrote: > > + > > + > > + > pg_report_log(logleveltext, > message anyelement[, ishidestmt > boolean ] [, detail text] [, > hint text] [, sqlstate >

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Thu, Nov 12, 2015 at 4:35 AM, Michael Paquier wrote: > On Sat, Oct 3, 2015 at 1:43 PM, dinesh kumar wrote: > > We can also use "PROGRAM 'cat > Output.csv' " to achieve this "NO READ > > ACCESS", since the program is always running as a instance

Re: [HACKERS] [PROPOSAL] DIAGNOSTICS = SKIPPED_ROW_COUNT

On Wed, Oct 14, 2015 at 4:06 PM, Robert Haas wrote: > On Wed, Oct 14, 2015 at 6:28 PM, dinesh kumar > wrote: > > I see this feature as an add on to do the parallel DML operations. > > There won't be any problem, if operations are mutually exclusive. > > I mean, ea

Re: [HACKERS] [PATCH] SQL function to report log message

On Thu, Oct 22, 2015 at 11:15 AM, Jim Nasby wrote: > On 10/22/15 2:20 AM, dinesh kumar wrote: > >> >> 2. Using this function, if we provide any "NULL" argument to the function, >> we should either skip it or report it. I see this is what the function &g

Re: [HACKERS] [PATCH] SQL function to report log message

Hi All, On Tue, Oct 20, 2015 at 1:22 PM, Pavel Stehule wrote: > > 2015-10-20 20:05 GMT+02:00 Robert Haas : > >> On Tue, Oct 20, 2015 at 11:29 AM, Pavel Stehule >> wrote: >> > 2015-10-20 17:15 GMT+02:00 Robert Haas : >> >> On Tue, Oct 20, 2015 at 11:09 AM, Pavel Stehule < >> pavel.steh...@gmail.

Re: [HACKERS] [PROPOSAL] DIAGNOSTICS = SKIPPED_ROW_COUNT

Hi Robert, On Wed, Oct 14, 2015 at 12:56 PM, Robert Haas wrote: > On Tue, Oct 13, 2015 at 10:37 PM, dinesh kumar > wrote: > > In an existing wait policies like WAIT(default) and NO WAIT, > > one can be sure to determine(Using ROW_COUNT daignostics counter), > > how

Re: [HACKERS] [PROPOSAL] DIAGNOSTICS = SKIPPED_ROW_COUNT

On Tue, Oct 13, 2015 at 5:53 AM, David G. Johnston < david.g.johns...@gmail.com> wrote: > >>> > Using this attribute, we can have more control on parallel operations >>> like, >>> >>> > IF SKIPPED_ROW_COUNT =0 THEN >>> > <> >>> > ELSE >>> > <> >>> > END IF; >>> >>> Um ... so what? This is not a u

Re: [HACKERS] Eclipse Help

On Tue, Oct 13, 2015 at 3:49 AM, Praveen M wrote: > Hi All, > > I was able to follow the debugging of the child process using this link, > https://wiki.postgresql.org/wiki/Working_with_Eclipse > > As per the notes , I was able to set breakpoints and everything seem to be > working (hopefully). Ho

Re: [HACKERS] [PROPOSAL] DIAGNOSTICS = SKIPPED_ROW_COUNT

On Mon, Oct 12, 2015 at 9:38 PM, Tom Lane wrote: > dinesh kumar writes: > > Would like to propose a new DIAGNOSTICS attribute, which returns the > no.of > > rows got skipped during the FOR UPDATE SKIP LOCKED; > > I'm concerned that there may not be any implementatio

[HACKERS] [PROPOSAL] DIAGNOSTICS = SKIPPED_ROW_COUNT

Hi Team, Would like to propose a new DIAGNOSTICS attribute, which returns the no.of rows got skipped during the FOR UPDATE SKIP LOCKED; Using this attribute, we can have more control on parallel operations like, IF SKIPPED_ROW_COUNT =0 THEN <> ELSE <> END IF; Kindly let me know your inputs/sugg

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Wed, Sep 2, 2015 at 1:19 PM, Stefan Kaltenbrunner < ste...@kaltenbrunner.cc> wrote: > On 09/02/2015 10:10 PM, dinesh kumar wrote: > > On Tue, Sep 1, 2015 at 10:58 PM, Stefan Kaltenbrunner > > mailto:ste...@kaltenbrunner.cc>> wrote: > > > > On

Re: [HACKERS] [PATCH] SQL function to report log message

On Thu, Sep 10, 2015 at 8:44 PM, Alvaro Herrera wrote: > dinesh kumar wrote: > > > Also, I was under impression that, all our TODO > > <https://wiki.postgresql.org/wiki/Todo> items are filtered for the real > use > > cases. Is my impression wrong. If I wa

Re: [HACKERS] [PATCH] SQL function to report log message

Hi All, Thanks for your inputs on this. Here, I see a conflict between the doable{RAISE}, and convenience{SQL function}, and will follow your inputs on this. Also, I was under impression that, all our TODO items are filtered for the real use cases. Is my i

Re: [HACKERS] [PATCH] SQL function to report log message

HI Robert, On Wed, Sep 9, 2015 at 8:30 PM, Robert Haas wrote: > On Wed, Jul 22, 2015 at 9:56 PM, dinesh kumar > wrote: > >> The real question is why the existing functionality in plpgsql isn't > >> sufficient. Somebody who wants a "log from SQL" function

Re: [HACKERS] [PATCH] SQL function to report log message

On Sun, Sep 6, 2015 at 4:46 PM, Pavel Stehule wrote: > > > 2015-09-06 13:12 GMT+02:00 dinesh kumar : > >> >> On Sun, Sep 6, 2015 at 4:00 PM, dinesh kumar >> wrote: >> >>> On Sun, Sep 6, 2015 at 3:39 PM, Pavel Stehule >>> wrote: >&g

Re: [HACKERS] [PATCH] SQL function to report log message

On Sun, Sep 6, 2015 at 4:00 PM, dinesh kumar wrote: > On Sun, Sep 6, 2015 at 3:39 PM, Pavel Stehule > wrote: > >> Hi >> >> attached patch with fixed broken error message >> >> Regards >> >> Pavel >> > > Hi Pavel, > > Thanks

Re: [HACKERS] [PATCH] SQL function to report log message

On Sun, Sep 6, 2015 at 3:39 PM, Pavel Stehule wrote: > Hi > > attached patch with fixed broken error message > > Regards > > Pavel > Hi Pavel, Thanks much for taking care of it. Patch looks great. -- Regards, Dinesh manojadinesh.blogspot.com

Re: [HACKERS] [PATCH] SQL function to report log message

Hi Pavel, On Sat, Sep 5, 2015 at 12:36 AM, Pavel Stehule wrote: > > > 2015-09-05 8:35 GMT+02:00 dinesh kumar : > >> >> >> On Fri, Sep 4, 2015 at 2:03 PM, Pavel Stehule >> wrote: >> >>> >>> >>> 2015-09-02 21:49 GMT+02:00 di

Re: [HACKERS] [PATCH] SQL function to report log message

On Fri, Sep 4, 2015 at 2:03 PM, Pavel Stehule wrote: > > > 2015-09-02 21:49 GMT+02:00 dinesh kumar : > >> On Mon, Aug 31, 2015 at 10:08 PM, Pavel Stehule >> wrote: >> >>> >>> >>> 2015-09-01 6:59 GMT+02:00 Pavel Stehule : >>> >

Re: [HACKERS] [PATCH] SQL function to report log message

On Fri, Sep 4, 2015 at 1:08 PM, Pavel Stehule wrote: > > > 2015-09-02 21:49 GMT+02:00 dinesh kumar : > >> On Mon, Aug 31, 2015 at 10:08 PM, Pavel Stehule >> wrote: >> >>> >>> >>> 2015-09-01 6:59 GMT+02:00 Pavel Stehule : >>> >

Re: [HACKERS] [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp

On Thu, Sep 3, 2015 at 9:48 PM, Andres Freund wrote: > Hi, > > On 2015-09-03 21:45:52 +0530, dinesh kumar wrote: > > Forcing VACUUM VERBOSE to write timestamp, for each "INFO" entry. This > was > > raised already in this > > < > http://www.pos

[HACKERS] [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp

Hi All, Greetings for the day. Would like to know your inputs/suggestions on below proposal. Kindly let me know, if it's already taken care. *Proposal* Forcing VACUUM VERBOSE to write timestamp, for each "INFO" entry. This was raised already in this

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Tue, Sep 1, 2015 at 10:58 PM, Stefan Kaltenbrunner < ste...@kaltenbrunner.cc> wrote: > On 07/25/2015 03:38 AM, dinesh kumar wrote: > > > > > > On Fri, Jul 24, 2015 at 10:22 AM, Robert Haas > <mailto:robertmh...@gmail.com>> wrote: > > > >

Re: [HACKERS] [PATCH] SQL function to report log message

On Mon, Aug 31, 2015 at 10:08 PM, Pavel Stehule wrote: > > > 2015-09-01 6:59 GMT+02:00 Pavel Stehule : > >> >> >> 2015-08-31 20:43 GMT+02:00 dinesh kumar : >> >>> Hi, >>> >>> On Sat, Aug 29, 2015 at 4:22 PM, Pavel Stehule >&g

Re: [HACKERS] [PATCH] SQL function to report log message

Hi, On Sat, Aug 29, 2015 at 4:22 PM, Pavel Stehule wrote: > Hi > > I am starting to work review of this patch > > 2015-07-13 9:54 GMT+02:00 dinesh kumar : > >> Hi All, >> >> Greetings for the day. >> >> Would like to discuss on below feature he

Re: [HACKERS] [PATCH] SQL function to report log message

On Sun, Aug 30, 2015 at 4:52 AM, Pavel Stehule wrote: > Hi > > I am starting to work review of this patch > > Hi Pavel, Thanks for your review. > 2015-07-13 9:54 GMT+02:00 dinesh kumar : > >> Hi All, >> >> Greetings for the day. >> >> Would l

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Fri, Jul 24, 2015 at 10:22 AM, Robert Haas wrote: > On Thu, Jul 23, 2015 at 8:15 PM, dinesh kumar > wrote: > > On Thu, Jul 23, 2015 at 9:21 AM, Robert Haas > wrote: > >> > >> On Thu, Jul 23, 2015 at 12:19 PM, dinesh kumar > > >> wrote: >

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

On Thu, Jul 23, 2015 at 9:21 AM, Robert Haas wrote: > On Thu, Jul 23, 2015 at 12:19 PM, dinesh kumar > wrote: > > Sorry for my unclear description about the proposal. > > > > "WITH PERMISSIVE" is equal to our existing behavior. That is, chmod=644 > on &

Re: [HACKERS] Proposing COPY .. WITH PERMISSIVE

Hi Robert/Andres, On Thu, Jul 23, 2015 at 8:34 AM, Robert Haas wrote: > On Thu, Jul 23, 2015 at 11:32 AM, Andres Freund > wrote: > > On 2015-07-23 11:26:27 -0400, Robert Haas wrote: > >> On Wed, Jul 22, 2015 at 11:29 PM, dinesh kumar > wrote: > >> > Would

Re: [HACKERS] [PATCH] SQL function to report log message

On Wed, Jul 22, 2015 at 8:56 PM, Michael Paquier wrote: > On Thu, Jul 23, 2015 at 10:56 AM, dinesh kumar > wrote: > > Hi All, > > > > On Mon, Jul 13, 2015 at 2:12 PM, Tom Lane wrote: > >> > >> Jim Nasby writes: > >> > On 7/13/15

[HACKERS] Proposing COPY .. WITH PERMISSIVE

Hi All, Would like to propose PERMISSIVE mode for the COPY created out files. I mean, at this moment, if do "COPY" as postgres instance owner, i can able to read the file as non instance user as well, and would like to restrict this to instance owner WITH PERMISSIVE option. Let me know your thoug

Re: [HACKERS] [PATCH] SQL function to report log message

Hi All, On Mon, Jul 13, 2015 at 2:12 PM, Tom Lane wrote: > Jim Nasby writes: > > On 7/13/15 3:39 PM, dinesh kumar wrote: > >> Ah. It's' my bad interpretation. Let me work on it, and will send a new > >> patch as a wrapper sql function for ereport. >

Re: [HACKERS] proposal: multiple psql option -c

On Thu, Jul 16, 2015 at 12:42 PM, Pavel Stehule wrote: > Hi > > can we support multiple "-c" option? > > Why? Because some statements like VACUUM cannot be used together with any > other statements with single -c option. The current solution is using echo > and pipe op, but it is a complication i

Re: [HACKERS] [PROPOSAL] VACUUM Progress Checker.

Hi On Wed, Jul 15, 2015 at 9:27 PM, Fujii Masao wrote: > On Thu, Jul 16, 2015 at 5:18 AM, Rahila Syed > wrote: > > Hello, > > > > Please find attached updated patch with an interface to calculate command > > progress in pgstat.c. > > Thanks for updating the patch! > > I got the following compil

Re: [HACKERS] [PATCH] SQL function to report log message

On Mon, Jul 13, 2015 at 1:56 PM, Jim Nasby wrote: > On 7/13/15 3:39 PM, dinesh kumar wrote: > >> I don't really see the point of what you're describing here. Just do >> something like RAISE WARNING which should normally be high enough to >> make it i

Re: [HACKERS] [PATCH] SQL function to report log message

On Mon, Jul 13, 2015 at 1:29 PM, Jim Nasby wrote: > On 7/13/15 12:39 PM, dinesh kumar wrote: > >> > As of now, we don't have an SQL function to write >> custom/application >> > messages to log destination. We have "RAISE" clause which is

Re: [HACKERS] [PATCH] SQL function to report log message

On Mon, Jul 13, 2015 at 1:11 AM, Michael Paquier wrote: > On Mon, Jul 13, 2015 at 4:54 PM, dinesh kumar > wrote: > > Would like to discuss on below feature here. > > > > Feature: > > Having an SQL function, to write messages to log destination. > > >

[HACKERS] [PATCH] SQL function to report log message

Hi All, Greetings for the day. Would like to discuss on below feature here. Feature: Having an SQL function, to write messages to log destination. Justification: As of now, we don't have an SQL function to write custom/application messages to log destination. We have "RAISE" clause whic

Re: [HACKERS] [PROPOSAL] VACUUM Progress Checker.

On Tue, Jun 30, 2015 at 1:07 PM, Rahila Syed wrote: > Hello Hackers, > > Following is a proposal for feature to calculate VACUUM progress. > > Use Case : Measuring progress of long running VACUUMs to help DBAs make > informed decision > whether to continue running VACUUM or abort it. > > +1 I am