Can anybody explain me, how to compile postgres source code in VC++.
Catch all the cricket action. Download
Yahoo! Score tracker
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> But we already have a recycling mechanism for pg_clog. AFAICS,
>> creating a parallel log file with a separate recycling mechanism is
>> a study in wasted effort.
> But that recycling requires the vacuum of every database in the syste
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > It only becomes better if we can throw away that file (or contents) when
> > the transaction completes and we have marked all the subtransactions as
> > completed. We can't compress pg_clog if we store the parent info in
> > there.
>
On 28 Nov 2002 at 10:45, Tom Lane wrote:
> "Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> > interesting thought. I think this boils down to how many knobs do we
> > need to put on this system. It might make sense to say allow upto X
> > concurrent vacuums, a 4 processor system might handle 4
Bruce Momjian <[EMAIL PROTECTED]> writes:
> It only becomes better if we can throw away that file (or contents) when
> the transaction completes and we have marked all the subtransactions as
> completed. We can't compress pg_clog if we store the parent info in
> there.
But we already have a recyc
Tom Lane wrote:
> > Isn't there some other way we can link these subtransactions together
> > rather than mucking with pg_clog, as we only need the linkage while we
> > mark them all committed?
>
> You *cannot* expect to do it all in shared memory; you will be blown out
> of the water by the first
Neil Conway <[EMAIL PROTECTED]> writes:
> I was looking at this a bit in IRC, and I was more concerned by the fact
> that 7.3 was 20% than 7.2 on the same hardware, when they both used the
> same query plan (consider the data at the end of the URL above, after
> the execution of 'SET enable_mergejo
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Also, I should point out that balooning pg_clog by 16x is going to mean
> we are perhaps 4-8x more likely to need extra pages to mark all
> subtransactions.
So? The critical point is that we don't need to serialize the pg_clog
operations if we do it tha
On Thu, 2002-11-28 at 21:23, Tom Lane wrote:
> wade <[EMAIL PROTECTED]> writes:
> > Explain output can be found at http://arch.wavefire.com/72v73a.txt
>
> The difference evidently is that 7.3 chooses a mergejoin where 7.2
> picks a hashjoin.
I was looking at this a bit in IRC, and I was more conc
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I should add that I am not prepared to overhaul the pg_clog file format
> > as part of adding subtransactions for 7.4. I can do the tid/sequential scan
> > method for abort, or the single-lock method described.
>
> If you think that
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I should add that I am not prepared to overhaul the pg_clog file format
> as part of adding subtransactions for 7.4. I can do the tid/sequential scan
> method for abort, or the single-lock method described.
If you think that changing the pg_clog file fo
wade <[EMAIL PROTECTED]> writes:
> While playing with one of my DBs under 7.3 to make use of its better
> explain features, I came across a query that runs significantly slower
> under 7.3 than
> 7.2.3. At first, I thought it would be a hardware issue, so i installed both
> versions on the same
I should add that I am not prepared to overhaul the pg_clog file format
as part of adding subtransactions for 7.4. I can do the tid/sequential scan
method for abort, or the single-lock method described.
---
Tom Lane wrote:
While playing with one of my DBs under 7.3 to make use of its better
explain features, I came across a query that runs significantly slower
under 7.3 than
7.2.3. At first, I thought it would be a hardware issue, so i installed both
versions on the same box.
7.2.3 tends to run the query in 80%
Anyone know why the install target in doc/src/Makefile is coded like
this:
install:
$(MAKE) all
(mv -f *.$(ZIPSUFFIX) ..)
and not the more conventional
install: all
mv -f *.$(ZIPSUFFIX) ..
or perhaps safer,
install: all
mv -f $(TARGETS) ..
I just typed "make al
Hannu Krosing <[EMAIL PROTECTED]> writes:
> On Thu, 2002-11-28 at 17:34, Evgen Potemkin wrote:
>> understanding SQL99 draft is a bit more difficult than i thought :)
> You might also try to get DB2 installed somewhere (IIRC IBM gives out
> limited time developer copies).
Even without DB2 install
Neil Conway <[EMAIL PROTECTED]> writes:
>> Has anyone of you a good pointer to a description of where in the system
>> tables I may find what informations?
> The PostgreSQL Developer's Guide has some information:
> http://developer.postgresql.org/docs/postgres/catalogs.html
> But IIRC it mig
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, locking is one possible solution, but no one likes that. One hack
> lock idea would be to create a subtransaction-only lock, so if you see
> the special 4-th xact state (about to be committed as part of a
> subtransaction) you have to wait on that l
Masaru Sugawara <[EMAIL PROTECTED]> writes:
> As for some current_*** functions, "select current_user;" seems to
> work, but "select current_user();" doesn't .
Complain to the SQL spec authors --- they mandated this peculiar keyword
syntax for what is really a function call.
On Thu, 2002-11-28 at 17:34, Evgen Potemkin wrote:
> thanks, it's VERY helpful.
> understanding SQL99 draft is a bit more difficult than i thought :)
You might also try to get DB2 installed somewhere (IIRC IBM gives out
limited time developer copies).
It implements at least the basic recursive q
On Thu, 2002-11-28 at 11:12, Steve Jackson wrote:
> Is there any deeper description of the "record" type in plpgsql?
Other than in the PL/PgSQL documentation, you mean? I dunno, the code, I
guess :-)
What specific information are you looking for?
Cheers,
Neil
--
Neil Conway <[EMAIL PROTECTED]>
pgman wrote:
> > AFAICS the problem lies in updating several pg_clog bits at once. How
> > can this be done without holding a potentially long lasting lock?
>
> Yes, locking is one possible solution, but no one likes that. One hack
> lock idea would be to create a subtransaction-only lock, so if
On Thursday 28 November 2002 00:18, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Ian Barwick writes:
> >> "Casting integers to boolean (for example, 0::bool) is no longer
> >> allowed, use '0'::bool instead".
> >
> > This advice would probably only cause more confusion, becaus
On Thursday 28 November 2002 00:32, Steve Jackson wrote:
> Hi
>
> Has anyone of you a good pointer to a description of where in the system
> tables I may find what informations? I try to code a generic procedure
> which gets information (like field type, field length, foreign keys...)
> about table
On Thu, 2002-11-28 at 02:32, Steve Jackson wrote:
> Has anyone of you a good pointer to a description of where in the system
> tables I may find what informations?
The PostgreSQL Developer's Guide has some information:
http://developer.postgresql.org/docs/postgres/catalogs.html
But IIRC it
See:
http://www.us.postgresql.org/users-lounge/docs/7.2/postgres/catalogs.html
for PostgreSQL 7.2.x, for 7.3 see:
http://developer.postgresql.org/docs/postgres/catalogs.html
Lee.
Steve Jackson writes:
> Hi
>
> Has anyone of you a good pointer to a description of where in the system
> t
Manfred Koizar wrote:
> On Wed, 27 Nov 2002 22:47:33 -0500 (EST), Bruce Momjian
> <[EMAIL PROTECTED]> wrote:
> >The interesting issue is that if we could set the commit/abort bits all
> >at the same time, we could have the parent/child dependency local to the
> >backend --- other backends don't nee
thanks, it's VERY helpful.
understanding SQL99 draft is a bit more difficult than i thought :)
regards,
---
.evgen
On 27 Nov 2002, Hannu Krosing wrote:
> I attach a railroad diagram of SQL99 "WITH RECURSIVE" and a diff against
> mid-summer gram.y which implements half of SQL99 _syntax_ (just th
Hi there!
Patch itself posted to pgsql-patches.
This is a new version of patch i've posted.
This for PG version 7.3rc1.
Changed syntax, now it's more closer to Oracle's and allows operator other
than '='.
Removed Const/Var trick, now it's a new FakeVar node used, as a side effect
it's not need i
Hi all
Is there any deeper description of the "record" type in plpgsql?
I try to iterate through whole rows and fields, but there is nearly nothing
written down, or at least I am finding nearly nothing.
Any help?
Thanks,
sj
---(end of broadcast)---
Hi
Has anyone of you a good pointer to a description of where in the system
tables I may find what informations? I try to code a generic procedure
which gets information (like field type, field length, foreign keys...)
about tables and fields from a system table.
Thank you for your help in adv
Hello,
Command Prompt, Inc. looks forward to the open source release of
PostgreSQL 7.3 as we are testing our commercial version of Mammoth
PostgreSQL 7.3. The updated
release of the core PostgreSQL code base has added many of the much
needed, and left behind feature such as drop column. The
How about "PostgreSQL, slightly less nightmares than the other databases"
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
How about OPTIMIZE?
eg. optimize customers
instead of analyze, could be paired with agressive
so, OPTIMIZE AGREESSIVE
very much a glass half empty, half full type thing. vacuum is not a
problem, its a solution.
Merlin
""Curtis Faith"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">
Just for the humor of it, as well as to confirm Nick's perspective,
years ago on our inhouse developed Burroughs mainframe dbms, we had a
process called "garbage collect".
Nicolai Tufar wrote:
I always wandered if VACUUM is the right name for the porcess. Now, when
PostgreSQL
is actively challe
>
> Hmm, ever tried using a large multiuser database such as a finance
> system using a Foxpro database? Network managers have been known to
> murder for less... :-)
>
Hmm, I have, and you could imagine the result :)
It was a small system, really and everything was fine until I added my 10th
user.
Force the system to use it as a function.
select "current_user"();
On Thu, 2002-11-28 at 11:31, Masaru Sugawara wrote:
> Hi,
>
> As for some current_*** functions, "select current_user;" seems to
> work, but "select current_user();" doesn't . Though current_user is
> defined as one of functions
Hi,
As for some current_*** functions, "select current_user;" seems to
work, but "select current_user();" doesn't . Though current_user is
defined as one of functions, why does such an error occur ?
renew=# select current_user();
ERROR: parser: parse error at or near "(" at character 20
Rega
Hans-Jürgen Schönig wrote:
> Is there going to be a way to use transactions inside transactions of
> transactions?
> In other words:
>
> BEGIN;
> BEGIN;
> BEGIN;
> BEGIN;
>
> COMMIT;
> COMMIT;
> COMMIT;
> COMMIT;
>
> Is there a way to have some sort of recursive
When doing an alter table .. add primary key operation on columns which
are not marked as null, would it be appropriate to mark the primary key
columns not null?
This follows with create table auto-marking columns null for primary
keys.
rbt=# \d ar
Table "public.ar"
Column | Type | Modifie
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> interesting thought. I think this boils down to how many knobs do we
> need to put on this system. It might make sense to say allow upto X
> concurrent vacuums, a 4 processor system might handle 4 concurrent
> vacuums very well.
This is almost c
On 27 Nov 2002 11:51:13 -0500, Neil Conway <[EMAIL PROTECTED]> wrote:
>Somewhat -- SQL2003 defines sequence generators that are pretty much
>identical in functionality to PostgreSQL's sequences, although the
>syntax is a bit different. I submitted a patch for 7.4 that adjusts the
>CREATE SEQUENCE g
On Wed, 27 Nov 2002 22:47:33 -0500 (EST), Bruce Momjian
<[EMAIL PROTECTED]> wrote:
>The interesting issue is that if we could set the commit/abort bits all
>at the same time, we could have the parent/child dependency local to the
>backend --- other backends don't need to know the parent, only the
>
[EMAIL PROTECTED] writes:
> Due to the 32 character limit on column/table names, we needed to recompile
>PostgreSQL from the source with updated settings. It compiles fine, but on running
>initdb, we get the following output:
Without bothering to examine the details, I'll bet you didn't do a fu
Is there going to be a way to use transactions inside transactions of
transactions?
In other words:
BEGIN;
BEGIN;
BEGIN;
BEGIN;
COMMIT;
COMMIT;
COMMIT;
COMMIT;
Is there a way to have some sort of recursive solution with every
transaction but the first one being a child
On Thu, 2002-11-28 at 01:58, Shridhar Daithankar wrote:
> There are differences in approach here. The reason I prefer polling rather than
> signalig is IMO vacuum should always be a low priority activity and as such it
> does not deserve a signalling overhead.
>
> A simpler way of integrating wo
46 matches
Mail list logo
