* Achmad Amin [EMAIL PROTECTED] [2002-09-05 22:54 -0700]:
Dear all,
I want to make library for visual basic to connect to
PostgreSQL, but I have problem to get libpq.dll source
code. Can somebody help me ?
Download a PostgreSQL source distribution. The libpq sources are in
Hello, All
I have read the source code /cvsroot/pgsql/src/backend/optimizer/path/costsize.c
and there is a function cost_sort(...). I think the code in 464 to 465 lines must be
changed to:
startup_cost += npageaccesses *
(1.0 + cost_nonsequential_access(1)) * 0.5;
The
Hi Yury,
This question should not be posted to -patches, changed accordingly.
What happens if you go 'VACUUM VERBOSE FULL goods;'?
Your on-disk files won't shrink or have unused tuples removed unless you
VACUUM FULL. The problem with doing VACUUM FULL is that it totally locks
the whole table
Hello!
On Fri, 6 Sep 2002, Christopher Kings-Lynne wrote:
This question should not be posted to -patches, changed accordingly.
What happens if you go 'VACUUM VERBOSE FULL goods;'?
Oh, big thanx!
But 'VACUUM VERBOSE FULL goods;' didn't work, only 'VACUUM FULL VERBOSE
goods;' did.:)
I make a
On Fri, 2002-09-06 at 07:37, Curt Sampson wrote:
On 5 Sep 2002, Hannu Krosing wrote:
Suppose you have a table CITIZEN with table-level constraint IS_GOOD
which is defined as kills_not_others(CITIZEN). and there is table
CIVIL_SERVANT (..) UNDER CITIZEN. Now you have just one table
I make a guess I've got this due to parallel running of a program making
bulk INSERTs/UPDATEs into that table. Mmm...I need a way to avoid the big
number of unused pages in such a case. LOCK TABLE?
Well, I suggest doing a normal vacuum analyze ('VACUUM ANALYZE goods') after
every bulk
I make a guess I've got this due to parallel running of a program making
bulk INSERTs/UPDATEs into that table. Mmm...I need a way to avoid the big
number of unused pages in such a case. LOCK TABLE?
Only UPDATEs and DELETEs (and rolled back INSERTs) cause unused pages.
The trick for other
On 6 Sep 2002, Hannu Krosing wrote:
In most object-oriented languages (Eiffel being a notable exception, IIRC),
you can't specify constraints on objects. But in a relational database,
you can specify constraints on tables, and it should *never* *ever* be
possible to violate those
On Fri, 6 Sep 2002, Christopher Kings-Lynne wrote:
There also seems to be a more complete list of english stopwords here:
http://www.dcs.gla.ac.uk/idom/ir_resources/linguistic_utils/
Chris, I think we have to separate stop word list from tsearch package and
supply just some defaults. The
On Fri, 6 Sep 2002, Christopher Kings-Lynne wrote:
Looking at the list of stopwords you sent me, Oleg, there are only about 1
out of the list of 120 stopwords that need to have all word forms
added. I
also don't think it'll be a maintenance problem. The reason I
think this is
On Fri, 6 Sep 2002, Christopher Kings-Lynne wrote:
Should we check for stop words before stemming or after ?
I think you should.
In the first case we have to collect all forms of stop-words
which is doable
but difficult to maintain, in latter - we'll have current problem.
Looking at
On Fri, 2002-09-06 at 09:53, Curt Sampson wrote:
If the language specifies that contstraints on tables are not to be
violated, then don't use those constraints when you don't want them.
But what _should_ i use then if i want the same business rule on most
top-level types, but a changed one
Seems to build cleanly here now. Perhaps anoncvs just hadn't sync'd up
when you tried Jason?
Regards, Dave.
-Original Message-
From: Jason Tishler [mailto:[EMAIL PROTECTED]]
Sent: 05 September 2002 20:38
To: Peter Eisentraut
Cc: Bruce Momjian; Dave Page; pgsql-hackers;
Well, I swear, this is the first release we've actually kept on scheduale
with, as far as going into beta is concerned ...
We've just packaged up and released v7.3beta1 for broader testing ... and
this is a big one as far as changes are concerned.
Major changes in this release:
Schemas
ljguo_1234 [EMAIL PROTECTED] writes:
I have read the source code
/cvsroot/pgsql/src/backend/optimizer/path/costsize.c and there is a function
cost_sort(...). I think the code in 464 to 465 lines must be changed to:
startup_cost += npageaccesses *
(1.0 +
On Thu, 2002-09-05 at 15:51, Hannu Krosing wrote:
On Fri, 2002-09-06 at 03:19, Greg Copeland wrote:
What about the concept of columns being public or private? That is,
certain columns may not be inherited by a child? Any thought to such a
concept? Perhaps different types of table
Peter,
On Fri, Sep 06, 2002 at 12:54:13PM +0100, Dave Page wrote:
Seems to build cleanly here now.
And here (and now) too.
Perhaps anoncvs just hadn't sync'd up when you tried Jason?
I guess so -- very strange...
Anyway, sorry (again) for the noise and thanks for fixing the Cygwin
build.
On Fri, 2002-09-06 at 07:53, Hannu Krosing wrote:
On Fri, 2002-09-06 at 09:53, Curt Sampson wrote:
This looks like a classic case of incorrect modelling to me. Does the
good itself change when it becomes a campaign_good? No. The price
changes, but that's obviously not an integral part of
On Fri, 2002-09-06 at 01:19, Christopher Kings-Lynne wrote:
OK,
The argument about using ALTER TABLE/ADD FOREIGN KEY in dumps was that it
caused an actual check of the data in the table, right? This was going to
be much slower than using CREATE CONSTRAINT TRIGGER.
So, why can't we do
On Fri, 2002-09-06 at 07:37, Curt Sampson wrote:
On 5 Sep 2002, Hannu Krosing wrote:
Suppose you have a table CITIZEN with table-level constraint IS_GOOD
which is defined as kills_not_others(CITIZEN). and there is table
CIVIL_SERVANT (..) UNDER CITIZEN. Now you have just one table
Tom Lane writes:
Rod Taylor [EMAIL PROTECTED] writes:
SunOS control.shared2 5.7 Generic_106541-20 sun4u sparc SUNW,Ultra-5_10
shows an error in ALTER TABLE tests:
ALTER TABLE FKTABLE ADD FOREIGN KEY(ftest1) references
pktable(ptest1);
NOTICE: ALTER TABLE will create implicit
Well I spent half a day and half a night, pgsql compiles ok for
me. However I'm still figuring why I have majodormo probs...
So I went back for now.
Regards
On 5 Sep 2002, Larry Rosenman wrote:
Date: 05 Sep 2002 15:16:38 -0500
From: Larry Rosenman [EMAIL PROTECTED]
To: Tom Lane [EMAIL
On Fri, 2002-09-06 at 08:57, [EMAIL PROTECTED] wrote:
On Fri, 2002-09-06 at 07:37, Curt Sampson wrote:
On 5 Sep 2002, Hannu Krosing wrote:
To elaborate on Gregs example if you have table GOODS and under it a
table CAMPAIGN_GOODS then you may place a general overridable constraint
Oops! [EMAIL PROTECTED] (Greg Copeland) was seen spray-painting on a wall:
--=-eu74lKXry3SVx8eZ/qBD
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Fri, 2002-09-06 at 08:57, [EMAIL PROTECTED] wrote:
On Fri, 2002-09-06 at 07:37, Curt Sampson wrote:
On 5 Sep 2002,
There was a comment earlier that was not really addressed.
What can you do with table inheritance that you can not do
with a relational implementation? Or what would work *better*
as inheritance? (you define better)
This is a genuine question, not a snarky comment. I really
want to know.
Hello all,
PostgreSQL *still* has a bug where PQcmdStatus() won't return the
number of rows updated. But that is essential for applications, since
without it of course we don't know if the updates/delete/insert
commands succeded. Even worst, on interfaces like Delphi/dbExpress the
program will
Hello Barry,
JDBC driver must find autocommit (off or on) and set autoCommit field
when open connection.
regards
On Friday 06 September 2002 06:52 pm, Barry Lind wrote:
Haris,
You can't use jdbc (and probably most other postgres clients) with
autocommit in postgresql.conf turned off.
Steve Howe wrote:
Hello all,
PostgreSQL *still* has a bug where PQcmdStatus() won't return the
number of rows updated. But that is essential for applications, since
without it of course we don't know if the updates/delete/insert
commands succeded. Even worst, on interfaces like
On Fri, 2002-09-06 at 11:05, [EMAIL PROTECTED] wrote:
Oops! [EMAIL PROTECTED] (Greg Copeland) was seen spray-painting on a wall:
That's a pretty forcible constraint. :-).
=20
Is there something broken with your mailer? It's reformatting quotes
rather horribly...
Hmm...not that I know
Marc G. Fournier writes:
Actually, I just asked for the split, I think it was peter that actually
did it ... :)
I recall that you thought of the split in order to save bandwidth for
those who didn't need everything. It was expressedly intended that the
-base tarball was usable by itself and
Hello Bruce,
Friday, September 6, 2002, 3:22:13 PM, you wrote:
BM Steve Howe wrote:
Hello all,
PostgreSQL *still* has a bug where PQcmdStatus() won't return the
number of rows updated. But that is essential for applications, since
without it of course we don't know if the
In testing the new 7.3 prepared statement functionality I have come
across some findings that I cannot explain. I was testing using PREPARE
for a fairly complex sql statement that gets used frequently in my
applicaition. I used the timing information from:
show_parser_stats = true
Haris,
You can't use jdbc (and probably most other postgres clients) with
autocommit in postgresql.conf turned off.
Hackers,
How should client interfaces handle this new autocommit feature? Is it
best to just issue a set at the beginning of the connection to ensure
that it is always on?
I am not any happier about it than you are. Your report is good because
it is the first case where returning the wrong value actually breaks
software. You may be able to justify adding a fix during beta by saying
it is a bug fix.
Of course, someone is going to have to generate a patch and
Barry Lind wrote:
Haris,
You can't use jdbc (and probably most other postgres clients) with
autocommit in postgresql.conf turned off.
Hackers,
How should client interfaces handle this new autocommit feature? Is it
best to just issue a set at the beginning of the connection to ensure
Hello Bruce,
Friday, September 6, 2002, 9:52:18 PM, you wrote:
BM I am not any happier about it than you are. Your report is good because
BM it is the first case where returning the wrong value actually breaks
BM software. You may be able to justify adding a fix during beta by saying
BM it
Hello Bruce,
Friday, September 6, 2002, 10:58:13 PM, you wrote:
BM Well, there was a big discussion, and I did bring up the issue in early
BM August to see if I could get a resolution to it and was told no
BM conclusion could be made.
BM I suggest you read the TODO detail on the item and make
37 matches
Mail list logo
