RE: Not able to insert data into table

From: "Vianello, Daniel A" <Daniel(dot)Vianello(at)charter(dot)com>
To: "shruti(dot)gupta(at)newgen(dot)co(dot)in" <shruti(dot)gupta(at)newgen(dot)co(dot)in>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: Not able to insert data into table
Date: 2019-06-17 14:47:49
Message-ID: 5af88d88f55948459a1750de366bea1b@NCEMEXGP001.CORP.CHARTERCOM.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Shruti

You will probably have more luck with this question if you provide example code and the exact error message that you are receiving. It should also be directed to the general mailing list before the bugs list. The general mailing list address is pgsql-general(at)postgresql(dot)org(dot)
Dan

From: shruti(dot)gupta(at)newgen(dot)co(dot)in [mailto:shruti(dot)gupta(at)newgen(dot)co(dot)in]
Sent: Monday, June 17, 2019 12:51 AM
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Not able to insert data into table

Hi Team,
I have written 1 function (return void) for inserting data into table .
This function is compiled successfully but in running process it raised a exception .
I have tried same process with 1 new function that return some int4 value than function running successfully.
So I want to know if definition part of function is same in both the function than why I am getting these exceptions?
Please share some solution that I can use in my function.

Regards,
Shruti Gupta

Disclaimer :- This e-mail and any attachment may contain confidential, proprietary or legally privileged information. If you are not the original intended recipient and have erroneously received this message, you are prohibited from using, copying, altering or disclosing the content of this message. Please delete it immediately and notify the sender. Newgen Software Technologies Ltd (NSTL) accepts no responsibilities for loss or damage arising from the use of the information transmitted by this email including damages from virus and further acknowledges that no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of NSTL.

E-MAIL CONFIDENTIALITY NOTICE:
The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-06-17 15:29:49 Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build
Previous Message PG Bug reporting form 2019-06-17 08:04:06 BUG #15855: Using 'nextval' inside INSERT RULE in case of bulk data insertion.