Hi everyone,
Finally we found , the JDBC function we ever modified
contributed to this phenomenon, thanks of all.
Yours,
Wang Shuo
HighGo Software Co.,Ltd.
November 18, 2013
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
Hi hackers,
I used jdbc to connect to PostgreSQL ,and I found parse
nearly three
times of bind and execute.Is is normaly? What factors may
cause this result?
The OS is CentOS 5. The PG is 9.0.9. The JDBC is 9.2.
Yours,
Wang Shuo
HighGo
On 2013-11-18 11:39, Amit Kapila wrote:
On Mon, Nov 18, 2013 at 7:32 AM, wangs...@highgo.com.cn wrote:
Hi hackers,
I used jdbc to connect to PostgreSQL ,and I found parse
nearly three
times of bind and execute.Is is normaly?
Actually bind and execute should be
On 2013-10-10 02:10, Robert Haas wrote:
I agree with these concerns, as well as those raised by Tom Lane and
Fabien COELHO, and I think they indicate that we shouldn't accept
this
patch. So I'm marking this as Rejected.
On 2013-10-11 06:48, Jim Nasby wrote:
I see a use case for disabling
wangs...@highgo.com.cn wangs...@highgo.com.cn wrote:
I modified the code for this situation.I consider it very simple.
It will does not modify the table file, when the scale has been
increased exclusively.
Kevin Grittner kgri...@ymail.com wrote:
This patch would allow data in a column
On 09/13/2013 05:23, Peter Eisentraut wrote:
= create table test1 (a int constraint pk primary key, b text);
= create view test2 as select a, b from test1 group by a;
= alter table test1 drop constraint pk;
ERROR: 2BP01: cannot drop constraint pk on table test1 because other
objects depend on
于 2013-09-09 20:54, Peter Eisentraut 回复:
On 9/3/13 3:13 AM, wangs...@highgo.com.cn wrote:
Drop/build and disable/enable constraint has no fundamental
difference,
and could achieve the same purpose.What I do also more convenient
for
the user.
Recording the disabled constraints is easier than
于 2013-09-06 01:41, Jeff Janes 回复:
On Wed, Sep 4, 2013 at 10:06 PM, wangs...@highgo.com.cn wrote:
于 2013-09-04 23:41, Jeff Janes 回复:
On Tue, Sep 3, 2013 at 9:08 PM, wangs...@highgo.com.cn wrote:
Hi, Hackers!
I find that it takes a long time when I increase the scale of a
numeric
于 2013-09-04 19:30, Noah Misch 回复:
On Wed, Sep 04, 2013 at 12:08:48PM +0800, wangs...@highgo.com.cn
wrote:
I find that it takes a long time when I increase the scale of a
numeric
datatype.
By checking the code, I found that's because it needs to rewrite
that
table's file.
After checking that
于 2013-09-05 01:56, Robert Haas 回复:
On Tue, Sep 3, 2013 at 3:13 AM, wangs...@highgo.com.cn wrote:
于 2013-09-03 08:15, David Johnston 回复:
Jeff Davis-8 wrote
Is there any semantic difference between marking a constraint as
DISABLED and simply dropping it? Or does it just make it easier to
于 2013-09-04 23:41, Jeff Janes 回复:
On Tue, Sep 3, 2013 at 9:08 PM, wangs...@highgo.com.cn wrote:
Hi, Hackers!
I find that it takes a long time when I increase the scale of a
numeric
datatype.
By checking the code, I found that's because it needs to rewrite
that
table's file.
After
于 2013-09-03 08:15, David Johnston 回复:
Jeff Davis-8 wrote
Is there any semantic difference between marking a constraint as
DISABLED and simply dropping it? Or does it just make it easier to
re-add it later?
David Johnston wrote:
I cannot answer the question but if there is none then the main
Hi, Hackers!
I find that it takes a long time when I increase the scale of a numeric
datatype.
By checking the code, I found that's because it needs to rewrite that
table's file.
After checking that table's data file, I found only parameter n_header
changed.
And, I found the data in that
于 2013-08-30 21:27, Tom Lane 回复:
wangs...@highgo.com.cn writes:
In order to achieve enable/disable constraint name，I made a
few
modifications to the code.
First, someone used to build the constraints while building
table. Then inserting data must follow a certain order.
14 matches
Mail list logo
