The problem I have with VMWare is that for the cost of a licence plus the
additional hardware on the box running it (CPU power, RAM, etc.) I can buy a
second cheap machine, using VMWare doesn't appear to save me my biggest
overheads of training staff on Unix and cost of equipment (software and
hard
On 27 Nov 2002 at 8:21, Al Sutton wrote:
> The problem I have with VMWare is that for the cost of a licence plus the
> additional hardware on the box running it (CPU power, RAM, etc.) I can buy a
> second cheap machine, using VMWare doesn't appear to save me my biggest
> overheads of training staf
thanks in advance
_
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
_
Select your own custom email address for FREE! Get [EMAIL PROTECTED]
> > > I think it's great - but don't quote me on that. :)
> > >
> >
> > PostgreSQL. Because life's too short to learn Oracle.
>
> PostgreSQL. For those with more to do than babysit a database.
>
Ah, better. More orthogonal.
---(end of broadcast)-
David,
Most generic format you can get it out of SQL Server in is CSV
by using a DTS ( Export Data ) wizard to text format. Another
alternative is the bcp command line tool, which produces standardised formats
These are documented in SQL Books Online ( free download from Microsoft )
http://www.mi
I always wandered if VACUUM is the right name for the porcess. Now, when
PostgreSQL
is actively challenging in Enterprise space, it might be a good idea to give
it a more
enterprise-like name. Try to think how it is looking for an outside person
to see
us, database professionals hold lenghty discus
Ian Barwick <[EMAIL PROTECTED]> writes:
> Thanks for the explanation. I'm not screaming for a reversion ;-), but
> changing behaviour which was implicitly valid in previous
> versions is bound to cause a few people a little head scratching
> when converting applications to 7.3 (I'm sure I can't be
By accident I stumbled across the following paragraph in the August
2002 draft of SQL 2003:
If there are multiple instances of s
specifying the same sequence generator within a single
SQL-statement, all those instances return the same value for a
given row processed
Or just reorg.
Am Mittwoch, 27. November 2002 15:02 schrieb Nicolai Tufar:
> I always wandered if VACUUM is the right name for the porcess. Now, when
> PostgreSQL
> is actively challenging in Enterprise space, it might be a good idea to
> give it a more
> enterprise-like name. Try to think how it
On Wed, 2002-11-27 at 10:29, Manfred Koizar wrote:
> By accident I stumbled across the following paragraph in the August
> 2002 draft of SQL 2003:
>
> If there are multiple instances of s
> specifying the same sequence generator within a single
> SQL-statement, all those instance
In a similar vein, setting the way back machine to the mid 80s when I was
in the USAF and teaching the computer subsystem of the A-10 INS test
station, we had old reclaimed Sperry 1650 computers (the precursor to the
1750) that had come out of the 1960 era fire control systems on
battleships li
Neil Conway <[EMAIL PROTECTED]> writes:
> On Wed, 2002-11-27 at 10:29, Manfred Koizar wrote:
>> By accident I stumbled across the following paragraph in the August
>> 2002 draft of SQL 2003:
>>
>> If there are multiple instances of s
>> specifying the same sequence generator within a single
>> SQL
On Wed, 2002-11-27 at 08:21, Al Sutton wrote:
> The problem I have with VMWare is that for the cost of a licence plus the
> additional hardware on the box running it (CPU power, RAM, etc.) I can buy a
> second cheap machine, using VMWare doesn't appear to save me my biggest
> overheads of training
On Wed, 2002-11-27 at 12:24, Tom Lane wrote:
> I would think his point is that the above paragraph specifies behavior
> that is very definitely NOT like Postgres'.
Ah, I see now -- yeah, I misunderstood.
> > I submitted a patch for 7.4 that adjusts the
> > CREATE SEQUENCE grammar to match SQL2003
Neil Conway <[EMAIL PROTECTED]> writes:
> There's already a need to reform the way in which the next value of a
> sequence is produced (nextval() makes it difficult to get the dependancy
> information right); would it be a good idea to change it to be
> completely SQL compatible at the same time?
From: "Bruce Momjian" <[EMAIL PROTECTED]>
> And finally, I must abort tuple changes made by the aborted
> subtransaction. One way of doing that is to keep all relation id's
> modified by the transaction, and do a sequential scan of the tables on
> abort, changing the transaction id's to a fixed ab
Dan Langille wrote:
I have been looking at contrib/ltree in the PostgreSQL repository. I've
modified the code to allow / as a node delimiter instead of . which is the
default.
What is the reason for changing delimiter?
Below are the patches to make this change. I have also moved the
delimi
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> I am working with David Wheeler on DBD:pg and hope to have a release
> packaged up tomorrow.
Bruce, David,
I'm updating all the test scripts to properly use the standard DBI
testing env vars, e.g. DBI_DSN, DBI_USER, DBI_PASS, and to use
Test::More.
"Jason E. Stewart" <[EMAIL PROTECTED]> writes:
> "Bruce Momjian" <[EMAIL PROTECTED]> writes:
>
> > I am working with David Wheeler on DBD:pg and hope to have a release
> > packaged up tomorrow.
>
> Bruce, David,
>
> I'm updating all the test scripts to properly use the standard DBI
> testing en
> -Original Message-
> From: Nicolai Tufar [mailto:[EMAIL PROTECTED]]
> Sent: 27 November 2002 14:02
> To: [EMAIL PROTECTED]; PgSQL Performance ML
> Subject: Re: [PERFORM] [HACKERS] Realtime VACUUM, was:
> performance of insert/delete/update
>
>
> I always wandered if VACUUM is the ri
I've posted an Email to the list as to why I'm avoiding a move to linux
(cost of training -v- cost of database (free) + money saved from recycling
current DB machines).
My experience with PostgreSQL has always been good, and I beleive that we
can test any potential bugs that we may beleive are in
Solaris tests from Martin.
> Sorry for taking so long to run the tests, but I was out sick on Monday
> and yesterday was busy in a meeting for most of the day.
>
> The results are the same as for RC1 - the geometry test fails with
> the last decimal digit being off by one. I have attached the re
More on solaris tests from Martin.
> I just looked a bit further and there is a
> regress/expected/geometry-solaris-i386.out file which diffs cleanly with
> the regress/results/geometry.out file I generated. Perhaps the regression
> test isn't comparing with the right file.
>
> Martin
>
---
On Fri, 22 Nov 2002 00:32:46 -0500 (EST), Bruce Momjian
<[EMAIL PROTECTED]> wrote:
>I am going to work on nested transactions for 7.4.
> [...]
>And finally, I must abort tuple changes made by the aborted
>subtransaction. One way of doing that is to keep all relation id's
>modified by the transacti
On Wednesday, November 27, 2002, at 02:46 AM, Jason E. Stewart wrote:
David, could you take a look at 11quoting.t? I'm pretty sure you wrote
this test (didn't you?). I converted the array of tests to a hash
table so that I could give them names. However, I could only give the
tests names like 'o
On 27 Nov 2002 at 12:16, Teodor Sigaev wrote:
> Dan Langille wrote:
> > I have been looking at contrib/ltree in the PostgreSQL repository.
> > I've modified the code to allow / as a node delimiter instead of .
> > which is the default.
> What is the reason for changing delimiter?
My tree repres
On Wed, 27 Nov 2002, Tom Lane wrote:
> Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> > Linux q1
> >
> > dynacom=# EXPLAIN ANALYZE SELECT count(*) from noon;
> > NOTICE: QUERY PLAN:
>
> > Aggregate (cost=20508.19..20508.19 rows=1 width=0) (actual
> > time=338.17..338.17
> > rows=1 loo
I've been thinking about how to improve the performance of queries using
"WHERE x IN (subselect)" and "WHERE x NOT IN (subselect)".
In the existing implementation, the subquery result is rescanned to look
for a match to x each time the WHERE clause is executed; this essentially
makes it work like
Does this mean that in the future '342' may not be valid as an insert into a
numeric field and that we should be using 342 instead?
On Wednesday 27 November 2002 05:07 pm, (Via wrote:
> Ian Barwick writes:
> > "Casting integers to boolean (for example, 0::bool) is no longer allowed,
> > use '0'::
What is the reason for changing delimiter?
My tree represents a file system. Here are some entries:
Below are the patches to make this change. I have also moved the
delimiter to a DEFINE so that other customizations are easily done.
This is a work in progress.
It's good.
#define ISAL
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> Are there any reason to "fetch (and perhaps decompress) the TOAST entries"
> just to count(*) without any WHERE clause ?
It doesn't. That was my point...
regards, tom lane
---(end of broadcast)--
Hackers, David Wheeler and I have released DBD:pg 1.20 to CPAN and
gborg. That completes the last moved interface I am involved with.
---
David Wheeler wrote:
> The uploaded file
>
> DBD-Pg-1.20.tar.gz
>
> has entere
Okay folks, I just packaged her up, and fixed up the ftp site so that
everything points properly to it ... this way the mirrors get a chance to
pick it all up over night ...
I will be sending out the press release first thing in the morning ...
Please take a look around, and let me know if I've
> The difficulty is that it's not clear how to choose one of these four
> ways, short of planning the *entire* query from scratch all four ways :-(.
> This seems pretty grim. Approaches #2 and #3 could be handled as local
> transformations of the WHERE clause, but we couldn't choose which to use
>
On 27 Nov 2002 at 19:55, Teodor Sigaev wrote:
> Ok, I think it's a good extension. Let you prepare cumulative patch.
> Nevertheless, we have no chance to insert this to 7.3 release :(.
> Only for 7.3.1 or even 7.4.
Thanks. As for the 7.3 release, yes, it would be nice, but that was
not my goal
Hannu,
Using a Win32 platform will allow them to perform relative metrics. I'm not
looking for a statement saying things are x per cent faster than production,
I'm looking for reproducable evidence that an improvement offers y per cent
faster performance than another configuration on the same plat
Tom commmited fixes for i386 Solaris today. I assume it will be in
7.3.1.
---
Christopher Kings-Lynne wrote:
> Solaris tests from Martin.
>
> > Sorry for taking so long to run the tests, but I was out sick on Monday
> > a
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> What about in the case of a scalar subquery eg. SELECT x IN
> (1,2,3,4,54,56,6), when there maybe hundreds of scalars?
Unrelated to my present problem.
regards, tom lane
---(end of broadcast)-
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom commmited fixes for i386 Solaris today. I assume it will be in
> 7.3.1.
7.3, since AFAICT Marc hasn't wrapped same yet ...
regards, tom lane
---(end of broadcast)---
TIP 5: Ha
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, because we are now
moving into the direction that character strings are no longer acceptable
as numeric data.
Note that
28:11:2002
Hi,
I am not able to install Postgres on NT. If anybody has installed postgres on NT, please give me steps to that. I have read documentation about it, but unable to do that.
I want to know, how shall I
On Wed, 27 Nov 2002, Al Sutton wrote:
> Hannu,
>
> Using a Win32 platform will allow them to perform relative metrics. I'm not
> looking for a statement saying things are x per cent faster than production,
> I'm looking for reproducable evidence that an improvement offers y per cent
> faster perf
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, because we are now
> moving into the direction that character strings a
Great! This represents two major achievements for our release process.
First, we got the beta out in a relatively short period, and second, we
started development on the next release _before_ we finished the
previous one. Both are major achievements.
---
Manfred Koizar wrote:
> On Fri, 22 Nov 2002 00:32:46 -0500 (EST), Bruce Momjian
> <[EMAIL PROTECTED]> wrote:
> >I am going to work on nested transactions for 7.4.
> > [...]
> >And finally, I must abort tuple changes made by the aborted
> >subtransaction. One way of doing that is to keep all relati
Ken Hirsch wrote:
> From: "Bruce Momjian" <[EMAIL PROTECTED]>
> > And finally, I must abort tuple changes made by the aborted
> > subtransaction. One way of doing that is to keep all relation id's
> > modified by the transaction, and do a sequential scan of the tables on
> > abort, changing the tr
Hi,
Sorry to ask this question straight out but I wasn't sure where else to get an answer!
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:
-
On 27 Nov 2002 at 13:01, Matthew T. O'Connor wrote:
> On Wed, 2002-11-27 at 01:59, Shridhar Daithankar wrote:
> > I would not like postmaster forking into pgavd app. As far as possible, we
> > should not touch the core. This is a client app. and be it that way. Once we
> > integrate it into back
It's an option, but I can see it being a bit of an H-Bomb to kill an ant if
the Win32 source appears within the next 6 weeks.
I've played used cygwin before and I've always been uncomfortable with the
way it's integrated with Windows. It always came accross as something that
isn't really for the w
Hi,
i run 2 queries on 2 similar boxes (one running Linux 2.4.7, redhat 7.1
and the other running FreeBSD 4.7-RELEASE-p2)
The 2 boxes run postgresql 7.2.3.
I get some performance results that are not obvious (at least to me)
i have one table named "noon" with 108095 rows.
The 2 queries are:
q
Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> Linux q1
>
> dynacom=# EXPLAIN ANALYZE SELECT count(*) from noon;
> NOTICE: QUERY PLAN:
> Aggregate (cost=20508.19..20508.19 rows=1 width=0) (actual
> time=338.17..338.17
> rows=1 loops=1)
> -> Seq Scan on noon (cost=0.00..20237.95 ro
51 matches
Mail list logo
