> > That would depend on the OS. Not many 'pc-based unix' support over
> > 4 GB of memory, some don't even go that far.
>
> > By the way, I too wonder which supported OS platform would support
> > over 4GB of memory on a PC..
>
> Linux? I don't think there's any problem handling more than 4G
> me
On Wed, Jan 22, 2003 at 02:55:34PM -0400, Curtis Faith wrote:
>
> Hannu Krosing also wrote:
> > (also I dont think you can easily compile C source on a
> > C# compiler) ;/
>
> I don't think it makes much sense target a compiler that won't compile
> the source, therefore, if what you say is true,
Justin Clift wrote:
Greg Copeland wrote:
Have you tried IBM's OSS visualization package yet? Sorry, I don't seem
to recall the name of the tool off the top of my head (Data Explorer??)
but it uses OpenGL (IIRC) and is said to be able to visualize just about
anything. Anything is said to includ
Greg Copeland wrote:
Have you tried IBM's OSS visualization package yet? Sorry, I don't seem
to recall the name of the tool off the top of my head (Data Explorer??)
but it uses OpenGL (IIRC) and is said to be able to visualize just about
anything. Anything is said to include simple data over tim
I have been following the debate about the Windows build environment.
I would like to say that the build environment is not a real issue for
Windows developers. For the most part Windows developers will be happy
with a working binary and an interface library. The one is savvy enough
to want to
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > Why don't you just include them by default, otherwise if WITHOUT OIDS
> > appears in the CREATE TABLE command, then don't include them ?
>
> Well, adding a WITHOUT OIDS option to CREATE TABLE AS would be a new
> feature, which I don't have
[snip]
> For the disk case, why not have the start of the record
> contain an array of offsets to the start of the data for each
> column? It would only be necessary to have a list for
> variable fields.
>
> So (for instance) if you have 12 variable fields, you would
> store 12 integers at th
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> For the disk case, why not have the start of the record contain an array
> of offsets to the start of the data for each column? It would only be
> necessary to have a list for variable fields.
No, you'd need an entry for *every* column (or at least, eve
[snip]
> So (for instance) if you have 12 variable fields, you would
> store 12 integers at the start of the record.
Additionally, you could implicitly size the integers from the properties
of the column. A varchar(255) would only need an unsigned char to store
the offset, but a varchar(8) w
Josh Berkus <[EMAIL PROTECTED]> writes:
> I am very strongly in favor of this idea. I would personally prefer it if
> the Join collapsing parmeter could be set at query time through a SET
> statement, but will of course defer to the difficulty level in doing so.
I guess I failed to make it cle
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 22, 2003 4:18 PM
> To: Dann Corbit
> Cc: Steve Crawford; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Terrible performance on wide selects
>
>
> "Dann Corbit" <[EMAIL PROTECTE
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Why not waste a bit of memory and make the row buffer the maximum
> possible length?
> E.g. for varchar(2000) allocate 2000 characters + size element and point
> to the start of that thing.
Surely you're not proposing that we store data on disk that way.
Tom,
I am very strongly in favor of this idea. I would personally prefer it if
the Join collapsing parmeter could be set at query time through a SET
statement, but will of course defer to the difficulty level in doing so.
> Comments? In particular, can anyone think of pithy names for these
>
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 22, 2003 4:04 PM
> To: Dann Corbit
> Cc: Steve Crawford; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Terrible performance on wide selects
>
>
> "Dann Corbit" <[EMAIL PROTECTE
Sean Chittenden <[EMAIL PROTECTED]> writes:
> How about something that's runtime tunable via a SET/SHOW config var?
Er, that's what I was talking about.
> I know this is a can of worms, but what about piggy backing on an
> Oracle notation and having an inline way of setting this inside of a
> com
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Maybe I don't really understand the problem, but it seems simple enough
> to do it once for the whole query.
We already do cache column offsets when they are fixed. The code that's
the problem executes when there's a variable-width column in the table
-
> There's been some recent discussion about the fact that Postgres
> treats explicit JOIN syntax as constraining the actual join plan, cf
> http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/explicit-joins.html
>
> This behavior was originally in there simply because of lack of time
> to
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 22, 2003 3:15 PM
> To: Steve Crawford
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Terrible performance on wide selects
>
>
> Steve Crawford sent me some profiling results
Steve Crawford sent me some profiling results for queries involving wide
tuples (hundreds of columns).
> Done, results attached. nocachegetattr seems to be the likely suspect.
Yipes, you can say that again.
% cumulative self self total
time seconds seconds
There's been some recent discussion about the fact that Postgres treats
explicit JOIN syntax as constraining the actual join plan, cf
http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/explicit-joins.html
This behavior was originally in there simply because of lack of time to
consider alt
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 22 January 2003 20:30
> To: Didier Moens
> Cc: Dave Page; PostgreSQL Hackers Mailing List
> Subject: Re: [HACKERS] Foreign key wierdness
>
>
> > With two tables each containing some 20.000 entries, the fk creatio
> -Original Message-
> From: Didier Moens [mailto:[EMAIL PROTECTED]]
> Sent: 22 January 2003 16:05
> To: Dave Page
> Cc: Tom Lane; PostgreSQL Hackers Mailing List
> Subject: Re: [HACKERS] Foreign key wierdness
>
>
> I did some extensive testing using PostgreSQL 7.3.1 (logs and results
On Wed, 2003-01-22 at 14:23, Marc G. Fournier wrote:
> If anyone has any 'last minute' issues they would like to see in either,
> please speak now or forever hold your peace :)
>
Can someone post a "changelog" for these releases? Also what tags will
be created/used in CVS?
Robert Treat
-
Viacheslav N Tararin wrote:
>
> Hi.
>
> Exists in CVS Win32 port sources?
Not yet.
I sent patches for a native Win32 port of v7.2.1 out a few days ago.
It's sure a couple weeks away before something against current CVS HEAD
comes out of that.
You can find the patches at
http://www.janwieck.ne
[EMAIL PROTECTED] writes:
> I'd support making psql 7.3 and forward be aware of the backend they
> are connecting to, and support them being able to work against all 7.3+
> servers, but I still fail to see the pressing need for a backward-compatible
> version when the correct one is always shipp
Have you tried IBM's OSS visualization package yet? Sorry, I don't seem
to recall the name of the tool off the top of my head (Data Explorer??)
but it uses OpenGL (IIRC) and is said to be able to visualize just about
anything. Anything is said to include simple data over time to complex
medical C
Firebird uses a set of Borland command line tools and Borland's make,
which they give away as a free download. Even if you're compiling for
Windows, the build process uses Borland's command line "make". A batch
build script copies makefiles from a single source directory and spreads
them aro
Hannu Krosing asked:
> Does anyone know how MySQL and interbase/firebird do it ?
>
>From the MySQL web site for version 4.0:
"The Windows binaries use the Cygwin library. Source code for the
version of Cygwin we have used is available on this page."
I think this offers a very big opportunity to
Jan Wieck writes:
> We focused on porting the programs. The goal was to have PostgreSQL
> running native on Win32 for a user. Having a nice and easy maintainable
> cross platform config, build and test environment for the developers is
> definitely something that still needs to be done (hint, hint
Tom Lane writes:
> > With sufficiently blurred vision one might even find SQL99's clause
> > ::=
> > UNNEST
> > applicable. Or maybe not.
>
> Hm. I'm not sure what UNNEST does, but now that you bring SQL99 into
> the picture, what about WITH? That might solve the prob
Hi.
Exists in CVS Win32 port sources?
Thanks.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list clea
Didier Moens <[EMAIL PROTECTED]> writes:
> I did some extensive testing using PostgreSQL 7.3.1 (logs and results
> available upon request), and the massive slowdown is NOT related to
> qualified tablename syntax or (lack of) VACUUM ANALYZE, but to the
> following change :
> pgAdminII 1.4.2 :
>
I didn't see this make it to the list. I thought I would try again.
--
//\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
-- Forwarded message --
Dat
Several objects have issues where you can drop them while a dependent is
being created -- a good example is Domains (and types in general) -- but
I'll hunt down others later (languages?). The solution (as Tom stated
earlier) is to create a more generic lock tag.
1. Modify LOCKTAG to include 'cla
I'm running a little late on this, but we'd like to put out a release of
each of the above over the course of the next 2 weeks ...
What I'd like to aim for is v7.2.4 for Tuesday next week, and v7.3.2 for
the following week ... this way it doesn't pull efforts from one to get
the other out ...
If
This is a multi-part message in MIME format.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
I (Curtis Faith) previously wrote:
> > The Visual C++ Workspaces and Projects files are actually
> > text files that have a defined format. I don't think the format is
> > published but it looks pretty easy to figure out.
Hannu Krosing replied:
> will probably change between releases
Even if the
Hi guys,
Is there anyone here that's good with C++ and has a little bit of time
to add PostgreSQL support to a project?
There is a 4D visualisation program called Flounder:
http://www.enel.ucalgary.ca/~vigmond/flounder/
And it does some pretty nifty stuff. It takes in data sets (x, y, z,
time)
On Wed, 2003-01-22 at 11:11, [EMAIL PROTECTED] wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> > Is this very different from how it's done at present?
>
> Yes. :)
>
> I'd like to play Devil's Advocate a bit on the whole backward-compatible
> psql issue. First, I have not seen a
>>>[EMAIL PROTECTED] said:
> I'd support making psql 7.3 and forward be aware of the backend they
> are connecting to, and support them being able to work against all 7.3+
> servers, but I still fail to see the pressing need for a backward-compatible
> version when the correct one is a
On Wednesday 22 January 2003 02:01, Dann Corbit wrote:
> Maybe because most of the machines in the world (by a titanic landslide)
> are Windoze boxes.
On the desktop, yes. On the server, no. PostgreSQL is nore intended for a
server, no? I can see the utility in having a development installatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is this very different from how it's done at present?
Yes. :)
I'd like to play Devil's Advocate a bit on the whole backward-compatible
psql issue. First, I have not seen a lot of clamor for this sort of thing.
Second, psql comes bundled with th
On Wed, 2003-01-22 at 15:34, Curtis Faith wrote:
> tom lane writes:
> > You think we should drive away our existing unix developers
> > in the mere hope of attracting windows developers? Sorry, it
> > isn't going to happen.
>
> Tom brings up a good point, that changes to support Windows should
> > SHOW
> >
> >
> > I think 7.4 could and really should implement SHOW command similar to
> > MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
>
> Actually, in 7.4 I'd tell them to:
>
> select * from information_schema.tables;
>
> This is a far more portable metho
tom lane writes:
> You think we should drive away our existing unix developers
> in the mere hope of attracting windows developers? Sorry, it
> isn't going to happen.
Tom brings up a good point, that changes to support Windows should not
add to the tasks of those who are doing the bulk of the w
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Why don't you just include them by default, otherwise if WITHOUT OIDS
> appears in the CREATE TABLE command, then don't include them ?
Well, adding a WITHOUT OIDS option to CREATE TABLE AS would be a new
feature, which I don't have the time/i
On Wed, 2003-01-22 at 04:55, Antti Haapala wrote:
> SHOW
>
>
> I think 7.4 could and really should implement SHOW command similar to
> MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
Actually, in 7.4 I'd tell them to:
select * from information_schema.tables;
This
http://www.janwieck.net/win32_port/notes.win32-ports.txt
How to compile this Win32 port
1) Requirements and 1-time settings:
1.1) Visual C++
You need VC++ 6.0 on ServicePack 5.
Oooh no, not MS stuff plz :(
Dev-Cpp is cool open source IDE, tha using a mingw port of gcc.
http://www.bloodshed.net
Ups... i sent an early draft of my post by accident, sorry...
--
Antti Haapala
+358 50 369 3535
ICQ: #177673735
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTE
SHOW
I think 7.4 could and really should implement SHOW command similar to
MySQL. Listing tables/foreign keys/views and so isn't just psql problem,
but common to many interface implementations and maintenance tools. I
think it's wrong to rely on pg_* system tables on these.
If you think o
50 matches
Mail list logo
