Re: [HACKERS] PITR logging control program
On Fri, 2004-04-30 at 04:02, Bruce Momjian wrote: Let me also add that I am not terribly worried about having the feature to restore to an arbitrary point in time for 7.5. I would much rather have a good PITR solution that works cleanly in 7.5 and add it to 7.6, than to have retore to an arbitrary point but have a strained implementation that we have to revisit for 7.6. Interesting thought, I see now your priorities. Will read and digest over next few days. Thanks for your help and attention, Best regards, Simon Riggs ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Small OS ports Handheld devices
Rob Butler wrote: $369 for 4GB of storage in a compact flash card is not all that bad. $189 for 2.2GB is very reasonable when you consider the 512MB CF is going for $149! The current cheap workaround to get a Hitachi (ne IBM) 4GB microdrive is to buy a Creative Muvo2 4GB and open it up to extract the intact (OEM) 4GB drive. $200 in the US typically. Being a digital camera nerd, I pick up these things... now back to the usual traffic. Peter ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] PITR logging control program
Basically it is updating the logs as soon as it receives the notifications. Writing 16 MB of xlogs could take some time. In my experience with archiving logs, 16 Mb is on the contrary way too small for a single log. The overhead of starting e.g. a tape session is so high that you cannot keep up (a few seconds). Once the tape is streaming it is usually quite fast. So imho it is not really practical to have logs so small that they can fill in less that 20 seconds. Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Small OS ports Handheld devices
Are there some ports available to various devices? What is the lowest memory footprint PostgreSQL has achieved? [8Mb was last quote] How little disk space has anyone achieved? Is that an available port, or just a set of configure options? Is there a definitive list of supported ports? (for anything) Does PostgreSQL run on? - Windows 2003 (is that part of Win32 port as a defined target?) It definitly is there fro Windows Server 2003, in the new port. But since you are talking handhelds, are you possibly referring to Windows Mobile 2003? That is a whole different beast, and *not* included in the win32 part (no Win CE variants are) //Magnus ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for 7.5 feature completion
* Handle sync() by opening all file opened since the last fsync and fsync'ing those - Tom's got this one, as is the most crucial outstanding part Yes, this is defintly the largest part of the code missing. * Win32 installer - I believe Magnus already has something in this regard Yup. I'll try to clean it up a bit and post it soon. A question about this though - do we want the installer source (required to build the MSI - not the MSI itself, of course) in main CVS? I asked before how it's handled for RPMs etc, and had no response there (it was probably a bit too much inside other discussions). If it shuold not be included in the main code (say, on gborg instead), it really shouldn't hold up going beta on the main backend. Thoughts? * Win32 service - Rony offered to do this, but have not heard back. Not a major item, and I've already got an implementation from my previous port. Whomever does this in the end, it should not be a lot of code, and not very complicated. There are a zillion examples all over on code that does this (for example the SDK samples from MS), and it's not complicated stuff. * Fix problem were locale doesn't match host locale, requires passing more params to startup applications - SMOP I'm looking into a quick-fix (but not as quick as the hack I did earlier). If it's not too much work, expect it fairly shortly. The good looking fix will come out of the backend startup reorganisation/cleanup Claudio will eventually do :-) The stuff I'm looking at should not be more ugly than what's there now, but there was agreement that what's there now is a bit more complicated than necessary. All other issues are nicities or fixups, IMHO. There really isn't anything that needs farming out, just a matter of having the pieces fall into place. Agreed. //Magnus ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for 7.5 feature completion
Yes, it was vague. The question is now that we are a month away, do we want to target June 1, mid-June, or July 1. If I may humbly chime in here...there currently is no binary packing for the win32 port. Magnus is currently working on an installer/service manager (dubbed 'longer term' on the status page) that would be nice to see make it in before the feature freeze. Just a clearification here - I am only working on the installer. *Not* on the service manager integration code. That one is flagged for Rony, or Claudio has some code almost ready. I haven't touched that part. //Magnus ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] 7.5 features
Andrew Dunstan [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Not quite yet - yesterday I got hold of a windows box for the first time in months and had significant building problems (the symlink problem and others). This needs to be robust. I will be sending in some fixes in due course. A patch fixing those problems have already been submitted by Claudio Natoli. Perhaps you already knew that. Kind regards, Thomas Hallgren ---(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 cleanly
Re: [HACKERS] Small OS ports Handheld devices
It definitly is there fro Windows Server 2003, in the new port. But since you are talking handhelds, are you possibly referring to Windows Mobile 2003? That is a whole different beast, and *not* included in the win32 part (no Win CE variants are) Nor are they likely to be at a guess. I tried compiling libpq using eVC++ 4.0 with the PPC 2003 SDK the other day and got nowhere fast. Not having looked at the code, I think you are going to have a much easier time looking at npgsql and the Compact Framework, if you developer on the PPC and want just the client. I even think I saw some messages about there being support included in npgsql already, but I'm not sure. Even if not, it shouldn't be *all* that hard to get it running - probably significantly easier than libpq. //Magnus ---(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 cleanly
Re: [HACKERS] Small OS ports Handheld devices
-Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: 30 April 2004 11:40 To: Simon Riggs; [EMAIL PROTECTED] Subject: Re: [HACKERS] Small OS ports Handheld devices It definitly is there fro Windows Server 2003, in the new port. But since you are talking handhelds, are you possibly referring to Windows Mobile 2003? That is a whole different beast, and *not* included in the win32 part (no Win CE variants are) Nor are they likely to be at a guess. I tried compiling libpq using eVC++ 4.0 with the PPC 2003 SDK the other day and got nowhere fast. Regards, Dave ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Call for 7.5 feature completion
Am Freitag, 30. April 2004 12:45 schrieb Magnus Hagander: A question about this though - do we want the installer source (required to build the MSI - not the MSI itself, of course) in main CVS? We don't have any other packaging-related files in our CVS (for various good reasons), so I don't think the Windows installer should be in there. ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] 7.5 features
Thomas Hallgren said: Andrew Dunstan [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Not quite yet - yesterday I got hold of a windows box for the first time in months and had significant building problems (the symlink problem and others). This needs to be robust. I will be sending in some fixes in due course. A patch fixing those problems have already been submitted by Claudio Natoli. Perhaps you already knew that. There's yet to be agreement on how to fix this. See the hack that I used yesterday on the -win32 list. cheers andrew ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Small OS ports Handheld devices
-Original Message- From: Magnus Hagander [mailto:[EMAIL PROTECTED] Sent: 30 April 2004 13:01 To: Dave Page; Simon Riggs; [EMAIL PROTECTED] Subject: RE: [HACKERS] Small OS ports Handheld devices Not having looked at the code, I think you are going to have a much easier time looking at npgsql and the Compact Framework, if you developer on the PPC and want just the client. I even think I saw some messages about there being support included in npgsql already, but I'm not sure. Even if not, it shouldn't be *all* that hard to get it running - probably significantly easier than libpq. Yeah, I did consider that (I was one of the Npgsql hackers in the early days). Looks like it will actually make more sense *in this case* to use WinInet and write a middle tier in PHP though. Which is what I'm currently doing :-) Regards, Dave ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] New COPY commands in libpq
I read in the manual that the libpq functions PQputline(conn, cmd) and
PQendcopy(conn) have been deprecated and that PQputCopyData(conn, cmd,
sizeof(cmd)) and PQputCopyEnd(conn, msg) are the replacements.
I'm trying to convert a program that works just fine with the old
functions. I assume I'm missing a step here:
old C++ code:
CString cmd;
res = PQexec(conn, COPY segmentvalues FROM STDIN;);
if (PQresultStatus (res) != PGRES_COPY_IN)
{
PQclear (res);
return ns_DATABASEERROR;
}
else
PQclear(res);
cmd.Format(1\t\2\t{3,4,5}\n);
PQputline(conn, cmd);
cmd.Format(\\.\n);
PQputline(conn, cmd);
PQendcopy(conn);
New C++ code:
CString cmd, msg;
res = PQexec(conn, COPY segmentvalues FROM STDIN;);
if (PQresultStatus (res) != PGRES_COPY_IN)
{
PQclear (res);
return ns_DATABASEERROR;
}
else
PQclear(res);
cmd.Format(1\t\2\t{3,4,5}\n);
* PQputCopyData(conn, cmd, sizeof(cmd));
cmd.Format(\\.\n);
* PQputCopyData(conn, cmd, sizeof(cmd));
* PQputCopyEnd(conn, msg);
Old C++ code works, new stuff doesn't. Only line that have changed are
*'d.
The serverlog gives me the error: ERROR: Copy from STDIN failed:
CONTEXT: COPY segmentvalues, line 1: 1 ERROR: current
transaction is aborted, commands ignored until the end of transaction
block.
Can anyone point me in the right direction? There aren't any examples
of how to use the new code in the manual. I thought I was following
the written instructions correctly (but apparently am not).
Thanks.
-Tony
p.s. Running PostgreSQL 7.4.2 server on Fedora Linux. Client is a
Windows XP MS Visual C++ .NET using libpq.
---(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 cleanly
Re: [HACKERS] Call for 7.5 feature completion
On Fri, 30 Apr 2004, Peter Eisentraut wrote: Am Freitag, 30. April 2004 12:45 schrieb Magnus Hagander: A question about this though - do we want the installer source (required to build the MSI - not the MSI itself, of course) in main CVS? We don't have any other packaging-related files in our CVS (for various good reasons), so I don't think the Windows installer should be in there. Agreed ... put it as a project on PgFoundry ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(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 cleanly
Re: [HACKERS] Call for 7.5 feature completion
Marc G. Fournier wrote: On Fri, 30 Apr 2004, Peter Eisentraut wrote: Am Freitag, 30. April 2004 12:45 schrieb Magnus Hagander: A question about this though - do we want the installer source (required to build the MSI - not the MSI itself, of course) in main CVS? We don't have any other packaging-related files in our CVS (for various good reasons), so I don't think the Windows installer should be in there. Agreed ... put it as a project on PgFoundry ... That will also be a sensible place to publish RC Binary packages for people to test. cheers andrew ---(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 cleanly
Re: [HACKERS] New COPY commands in libpq
On Fri, Apr 30, 2004 at 06:12:35AM -0700, Tony Reina wrote:
CString cmd, msg;
cmd.Format(1\t\2\t{3,4,5}\n);
* PQputCopyData(conn, cmd, sizeof(cmd));
cmd.Format(\\.\n);
* PQputCopyData(conn, cmd, sizeof(cmd));
* PQputCopyEnd(conn, msg);
Old C++ code works, new stuff doesn't. Only line that have changed are
*'d.
I'm not surprised. CString is clearly a class, and cmd is an object of
that class. Apparently that class has an implicit conversion operator to
char * (which is a striking example of a Bad Idea--kids, don't try this
at home!) but nonetheless, sizeof() should still give you the size of the
object, *not* the size of the string it represents!
You might try porting your code to libpqxx, which is C++-native and should
make large swathes of this sort of code unnecessary.
Jeroen
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Current CVS tip segfaulting
On Fri, Apr 30, 2004 at 12:52:10AM -0400, Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: In current (as of a couple hours ago) clean CVS tip sources, without any of my local changes, I'm getting a postmaster segfault when trying to connect to a non existant database. Alvaro, did you figure this out? I've been mostly distracted for the past week ... No. I still see the failure on my platform but I don't know what to attribute it to. -- Alvaro Herrera (alvherre[a]dcc.uchile.cl) Hay quien adquiere la mala costumbre de ser infeliz (M. A. Evans) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] inconsistent owners in newly created databases?
Dear hackers, It seems to me that the current default setup for a new database which is given to some user is not consistent (createdb -O calvin foo or CREATE DATABASE foo WITH OWNER calvin). Indeed, although the database belongs to the owner, the public schema still belongs to the database super user, as it was the case in template1. As a consequence, the owner of the database CANNOT change the rights of the schema, hence he cannot prevent anyone from creating a new table in the public schema! However, has he owns the database, he can prevent user from creating temporary tables... Not really consistent. Dropping (the owner of a database can do that) and recreating the schema is not a real fix, because all installation performed on template1 (plpgsql, functions...) would be lost. So it seems to me that the public schema should also belong to the owner of the database. I cannot foresee all consequences, but the current situation is really inconsistent. Any comment? -- Fabien Coelho - [EMAIL PROTECTED] ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] pg ANY/SOME ambiguity wrt sql standard?
AFAICS this ambiguity is built into the SQL standard, and in fact it's possible to generate cases that are legally parseable either way: SELECT foo.x = ANY((SELECT bar.y FROM bar)) FROM foo; [...] So I think that the SQL committee shot themselves in the foot when they decided it was a good idea to call the boolean-OR aggregate ANY, and our addition of an array option isn't the fundamental problem. Anyone know if SQL2003 fixed this silliness? It does not seemed to be fixed in the copy I found, but it may not be the last version. As a temporary fix, what about _ANY and _SOME as aggregate names? -- Fabien Coelho - [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Current CVS tip segfaulting
Alvaro Herrera [EMAIL PROTECTED] writes: In current (as of a couple hours ago) clean CVS tip sources, without any of my local changes, I'm getting a postmaster segfault when trying to connect to a non existant database. Alvaro, did you figure this out? I've been mostly distracted for the past week ... No. I still see the failure on my platform but I don't know what to attribute it to. I also have that for a database installation from CVS on April 17. It also leaves the server in some incoherent state: Apr 30 17:58:22 sablons postgres[31629]: [31-1] FATAL: database toto does not exist Apr 30 17:58:22 sablons postgres[31604]: [31-1] LOG: server process (PID 31629) was terminated by signal 11 Apr 30 17:58:22 sablons postgres[31604]: [32-1] LOG: terminating any other active server processes Apr 30 17:58:22 sablons postgres[31532]: [31-1] WARNING: terminating connection because of crash of another server process Apr 30 17:58:22 sablons postgres[31532]: [31-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server Apr 30 17:58:22 sablons postgres[31532]: [31-3] process exited abnormally and possibly corrupted shared memory. Apr 30 17:58:22 sablons postgres[31532]: [31-4] HINT: In a moment you should be able to reconnect to the database and repeat your command. Apr 30 17:58:22 sablons postgres[31604]: [33-1] LOG: all server processes terminated; reinitializing Apr 30 17:58:22 sablons postgres[31630]: [34-1] LOG: database system was interrupted at 2004-04-30 17:54:56 CEST Apr 30 17:58:22 sablons postgres[31630]: [35-1] LOG: checkpoint record is at 0/B486F30 Apr 30 17:58:22 sablons postgres[31630]: [36-1] LOG: redo record is at 0/B486F30; undo record is at 0/0; shutdown TRUE Apr 30 17:58:22 sablons postgres[31630]: [37-1] LOG: next transaction ID: 10769; next OID: 123703 Apr 30 17:58:22 sablons postgres[31630]: [38-1] LOG: database system was not properly shut down; automatic recovery in progress Apr 30 17:58:22 sablons postgres[31630]: [39-1] LOG: redo starts at 0/B486F70Apr 30 17:58:22 sablons postgres[31630]: [40-1] PANIC: could not create relation 123703/16660: No such file or directory Apr 30 17:58:22 sablons postgres[31604]: [34-1] LOG: startup process (PID 31630) was terminated by signal 6 Apr 30 17:58:22 sablons postgres[31604]: [35-1] LOG: aborting startup due to startup process failure So it is not a clean coredump, if some may be;-) -- Fabien Coelho - [EMAIL PROTECTED] ---(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 cleanly
Re: [HACKERS] New COPY commands in libpq
[EMAIL PROTECTED] (Tony Reina) writes: * PQputCopyData(conn, cmd, sizeof(cmd)); I'm a bit rusty on C++ string mashing, but surely sizeof() is not the correct way to determine the number of bytes presently stored in a variable-length string? * PQputCopyEnd(conn, msg); You want to pass NULL for the second argument. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Current CVS tip segfaulting
I think we fixed it since then. --- Fabien COELHO wrote: Alvaro Herrera [EMAIL PROTECTED] writes: In current (as of a couple hours ago) clean CVS tip sources, without any of my local changes, I'm getting a postmaster segfault when trying to connect to a non existant database. Alvaro, did you figure this out? I've been mostly distracted for the past week ... No. I still see the failure on my platform but I don't know what to attribute it to. I also have that for a database installation from CVS on April 17. It also leaves the server in some incoherent state: Apr 30 17:58:22 sablons postgres[31629]: [31-1] FATAL: database toto does not exist Apr 30 17:58:22 sablons postgres[31604]: [31-1] LOG: server process (PID 31629) was terminated by signal 11 Apr 30 17:58:22 sablons postgres[31604]: [32-1] LOG: terminating any other active server processes Apr 30 17:58:22 sablons postgres[31532]: [31-1] WARNING: terminating connection because of crash of another server process Apr 30 17:58:22 sablons postgres[31532]: [31-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server Apr 30 17:58:22 sablons postgres[31532]: [31-3] process exited abnormally and possibly corrupted shared memory. Apr 30 17:58:22 sablons postgres[31532]: [31-4] HINT: In a moment you should be able to reconnect to the database and repeat your command. Apr 30 17:58:22 sablons postgres[31604]: [33-1] LOG: all server processes terminated; reinitializing Apr 30 17:58:22 sablons postgres[31630]: [34-1] LOG: database system was interrupted at 2004-04-30 17:54:56 CEST Apr 30 17:58:22 sablons postgres[31630]: [35-1] LOG: checkpoint record is at 0/B486F30 Apr 30 17:58:22 sablons postgres[31630]: [36-1] LOG: redo record is at 0/B486F30; undo record is at 0/0; shutdown TRUE Apr 30 17:58:22 sablons postgres[31630]: [37-1] LOG: next transaction ID: 10769; next OID: 123703 Apr 30 17:58:22 sablons postgres[31630]: [38-1] LOG: database system was not properly shut down; automatic recovery in progress Apr 30 17:58:22 sablons postgres[31630]: [39-1] LOG: redo starts at 0/B486F70Apr 30 17:58:22 sablons postgres[31630]: [40-1] PANIC: could not create relation 123703/16660: No such file or directory Apr 30 17:58:22 sablons postgres[31604]: [34-1] LOG: startup process (PID 31630) was terminated by signal 6 Apr 30 17:58:22 sablons postgres[31604]: [35-1] LOG: aborting startup due to startup process failure So it is not a clean coredump, if some may be;-) -- Fabien Coelho - [EMAIL PROTECTED] ---(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 cleanly -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [pgsql-advocacy] What can we learn from MySQL?
Andrew Payne wrote: My concern about a single company, as all of us are, is that we kill the community that created the software, which then burdens the single company to steer development, leading to disaster. Understood, and that's the potential catch-22. This is the problem with capital: no smart investor is going to fund a company to promote and support an project like Postgres if there's nothing to prevent 5 other investors and teams from doing the exact same thing. There MAY be a way to form something that's supportive and respectful of the community, and I think it's worth trying to figure that out. Bottom line: the Postgres project is at a stage where the non-technical factors (marketing, partnerships) are at least as important as the technical ones. Postgres may lose because of lacking technology (such as win32 support, though coming soon), but will not necessarily win with the best technology. Remember, we all came to PostgreSQL because of the community development, so we can't expect us to get excited about something that risks that just to win, as you say. If we had gone in this direction with Great Bridge, we would have seriously injured PostgreSQL and it might not be what it is today. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [pgsql-advocacy] What can we learn from MySQL?
Bruce wrote: Remember, we all came to PostgreSQL because of the community development, so we can't expect us to get excited about something that risks that just to win, as you say. If we had gone in this direction with Great Bridge, we would have seriously injured PostgreSQL and it might not be what it is today. The direction I think I'm suggesting is actually not all that different from Great Bridge. And to your point, Great Bridge failed yet Postgres still thrived. The difference is that you could now correct for Great Bridge's problems, which include but are not limited to: timing (4 years has changed a lot for commercial acceptance of open source), funding ($25m was too much), and strategy (this is not an quick attempt to copy Red Hat). I think such a project, with the right parameters, is very fundable. If anyone wants to talk about that, you should drop me an email off-list; we're probably stepping out of topic for the hacker and advocacy lists. -andy ---(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 cleanly
Re: [HACKERS] [pgsql-advocacy] What can we learn from MySQL?
The difference is that you could now correct for Great Bridge's problems, which include but are not limited to: timing (4 years has changed a lot for commercial acceptance of open source), funding ($25m was too much), and strategy (this is not an quick attempt to copy Red Hat). I think such a project, with the right parameters, is very fundable. If anyone wants to talk about that, you should drop me an email off-list; we're probably stepping out of topic for the hacker and advocacy lists. Why would someone fund a new PostgreSQL project when there are several viable commercial entities doing the job right now? J -andy ---(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 cleanly ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] pgsql-server/ /configure /configure.in rc/incl ...
Marc G. Fournier wrote: Well, that's an okay position if your time horizon is measured in days. But I would like to see us using that code on all platforms before 7.5 feature freeze. It's silly to be carrying that code around and not using it, when we have constant problems with the C-library-based time zone code, plus big portability issues arising from inconsistency of time zone names across platforms. For example, for the first time we'd be able to actually document the set of time zone names accepted by SET TIMEZONE, and *reliably* detect whether a provided name is really legal. Frankly I would never have accepted this patch if I thought it were going to be a Windows-only hack; I would have held out for something a lot smaller. In my mind the principal reason for having it is not Win32 at all, but solving the multi-platform problems we've always had with time zone handling. It goes with the Win32 approach of doing as little as possible to the Unix port. If the Unix folks want it, we can enable it, but the Win32 folks aren't going to force it on Unix until Unix wants it and has tested it. Unix wants it and is willing to spend the next month testing it to make sure its good :) OK, let me get it working on my Unix first and then I will give instructions for others on how to test it. Once a few have tested that it works, we can enable it for all ports and rip out the PGTZ tests. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Plan for feature freeze?
Marc G. Fournier wrote: No, I agree that that would be foolish ... but there has also been alot done on the code over the past few months that even *one* of those features should be enough to put it over the top ... OK, what is the plan for feature freeze? As we going for June 1, and making no adjustments? If we have no major features done, we still do June 1. Or are we waiting for one or several major features to complete and then set a freeze date? 1 of the major features that are currently on tap (ie. Win32) *or* June 1st, whichever happens to be the longer of the two ... Indications that I've seen through this discussion are that Win32 can, and should, be done by June 1st ...so extending may be a moot point anyway ... OK, but I am worried about giving Win32 special treatment, and having the date float like that until Win32 is done. This is what we did with the SMP fixed in 7.3 and the date slipped week by week. We have to set the date firm early on. I think we all agreed to that in the past. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 8: explain analyze is your friend
[HACKERS] Weird prepared stmt behavior
Hackers, Is this expected? If so, why? I'd expect the prepared stmt to be deallocated. alvherre=# begin; BEGIN alvherre=# prepare tres as select 3; PREPARE alvherre=# rollback; ROLLBACK alvherre=# execute tres; ?column? -- 3 (1 fila) -- Alvaro Herrera (alvherre[a]dcc.uchile.cl) FOO MANE PADME HUM ---(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 cleanly
[HACKERS] ecpg and the timezone database
Does ecpg need to use the same timezone database as the backend? I just committed code so it will not, but I am not sure. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Plan for feature freeze?
On Fri, 30 Apr 2004, Bruce Momjian wrote: Marc G. Fournier wrote: No, I agree that that would be foolish ... but there has also been alot done on the code over the past few months that even *one* of those features should be enough to put it over the top ... OK, what is the plan for feature freeze? As we going for June 1, and making no adjustments? If we have no major features done, we still do June 1. Or are we waiting for one or several major features to complete and then set a freeze date? 1 of the major features that are currently on tap (ie. Win32) *or* June 1st, whichever happens to be the longer of the two ... Indications that I've seen through this discussion are that Win32 can, and should, be done by June 1st ...so extending may be a moot point anyway ... OK, but I am worried about giving Win32 special treatment, and having the date float like that until Win32 is done. This is what we did with the SMP fixed in 7.3 and the date slipped week by week. We have to set the date firm early on. I think we all agreed to that in the past. No no ... the date isn't floating on Win32 ... the date is floating on one of the major features (PITR, 2PC, etc) ... if Win32 happens to be the first major feature, so be it, but it is not contigent on Win32 ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(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 cleanly
Re: [HACKERS] Plan for feature freeze?
Marc G. Fournier wrote: On Fri, 30 Apr 2004, Bruce Momjian wrote: Marc G. Fournier wrote: No, I agree that that would be foolish ... but there has also been alot done on the code over the past few months that even *one* of those features should be enough to put it over the top ... OK, what is the plan for feature freeze? As we going for June 1, and making no adjustments? If we have no major features done, we still do June 1. Or are we waiting for one or several major features to complete and then set a freeze date? 1 of the major features that are currently on tap (ie. Win32) *or* June 1st, whichever happens to be the longer of the two ... Indications that I've seen through this discussion are that Win32 can, and should, be done by June 1st ...so extending may be a moot point anyway ... OK, but I am worried about giving Win32 special treatment, and having the date float like that until Win32 is done. This is what we did with the SMP fixed in 7.3 and the date slipped week by week. We have to set the date firm early on. I think we all agreed to that in the past. No no ... the date isn't floating on Win32 ... the date is floating on one of the major features (PITR, 2PC, etc) ... if Win32 happens to be the first major feature, so be it, but it is not contigent on Win32 ... So you are floating the entire thing. I am tired of discussing this. You call the freeze and when it is a disaster, you can take the credit. I am not worrying about any freeze date anymore. You freeze whenever you want to. Floating a freeze data has always been a failure. Let's watch it happen again. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] regression failure on unix with new timezone library
I am seeing a hung regression test just after numerology on Unix. If you set USE_PGTZ to yes in Makefile.global and define USE_PGTZ in pg_config.h, you might see it too. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] [INTERFACES] ecpg and the timezone database
Does ecpg need to use the same timezone database as the backend? I just committed code so it will not, but I am not sure. I think it should not use it, for the following reasons: * When ecpg is used to write a program, this is a client program. I'd expect a client program to follow the timezone rules of the client (and other rules), and not the server. And it has to interface with any amount of other code that is linked only against the normal timezone libraries on the client. * Ecpg is used to write client programs. If it used the special pg timezone library, every client program written using ecpg would have to ship with the pg *timezone database* as well. I'm sure that's now what you'd want. But then again, I don't use ecpg myself, so others may certainly have better arguments in either direction. //Magnus ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Call for 7.5 feature completion
On Thu, Apr 29, 2004 at 09:30:12PM -0300, Marc G. Fournier wrote: June 1st, let's do beta for 7.5 and then branch onto 8.0, with 8.0 key'd to the Win32 Native port being finished ... I seem to remember the same argument at 7.4 time. I don't use Windows, I think it's a bletcherous system, but I really think delaying the Windows port Yet Again will make the project almost completely irrelevant to a significant audience. I completely agree that it'd be a bad idea to slip indefinitely on the basis of Windows is still not ready, but if it's a matter of changing freeze date by a month, given the long notice, why is that a bad thing? The Windows port is _extremely_ important for a lot of people, and I think it'd be short sighted to ignore that constituency, even if they are mostly not here yet. A -- Andrew Sullivan | [EMAIL PROTECTED] ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Plan for feature freeze?
Bruce Momjian said: Marc G. Fournier wrote: No no ... the date isn't floating on Win32 ... the date is floating on one of the major features (PITR, 2PC, etc) ... if Win32 happens to be the first major feature, so be it, but it is not contigent on Win32 ... So you are floating the entire thing. I am tired of discussing this. You call the freeze and when it is a disaster, you can take the credit. I am not worrying about any freeze date anymore. You freeze whenever you want to. Floating a freeze data has always been a failure. Let's watch it happen again. ISTM the issue is what freeze date is the sweet spot, that doen't hold us up endlessly but allows maximum chance to get in some of the features we badly need? My previous suggestion of mid June was based on my impressionistic balancing those 2 factors. Andrew Sullivan is right, though, about the bad press we would get from missing shipping the Win32 port - it would do a lot of damage after it has been talked up so much. Andrew ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] ecpg and the timezone database
Bruce Momjian said: Does ecpg need to use the same timezone database as the backend? I just committed code so it will not, but I am not sure. surely all clients should be utterly ignorant of what the backend uses? cheers andrew ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Plan for feature freeze?
Hello, Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. This could also lead to other things. For example if we have Win32 and PITR calling it 7.5 is a mistake (IMHO) it should be 8.0 etc... Sincerely, Joshua D. Drake Sincerely, Joshua D. Drake Bruce Momjian wrote: Marc G. Fournier wrote: On Fri, 30 Apr 2004, Bruce Momjian wrote: Marc G. Fournier wrote: No, I agree that that would be foolish ... but there has also been alot done on the code over the past few months that even *one* of those features should be enough to put it over the top ... OK, what is the plan for feature freeze? As we going for June 1, and making no adjustments? If we have no major features done, we still do June 1. Or are we waiting for one or several major features to complete and then set a freeze date? 1 of the major features that are currently on tap (ie. Win32) *or* June 1st, whichever happens to be the longer of the two ... Indications that I've seen through this discussion are that Win32 can, and should, be done by June 1st ...so extending may be a moot point anyway ... OK, but I am worried about giving Win32 special treatment, and having the date float like that until Win32 is done. This is what we did with the SMP fixed in 7.3 and the date slipped week by week. We have to set the date firm early on. I think we all agreed to that in the past. No no ... the date isn't floating on Win32 ... the date is floating on one of the major features (PITR, 2PC, etc) ... if Win32 happens to be the first major feature, so be it, but it is not contigent on Win32 ... So you are floating the entire thing. I am tired of discussing this. You call the freeze and when it is a disaster, you can take the credit. I am not worrying about any freeze date anymore. You freeze whenever you want to. Floating a freeze data has always been a failure. Let's watch it happen again. -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL
Re: [HACKERS] Plan for feature freeze?
Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. We could go for September 1st, which would mean most are back from holidays, in order to do beta testing ... and no, I'm not serious ... Why not? Seemed like a fairly good argument both yours and mine ;) Sincerely, Joshua D. Drake Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL
Re: [HACKERS] Plan for feature freeze?
On Fri, 30 Apr 2004, Joshua D. Drake wrote: Hello, Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. We could go for September 1st, which would mean most are back from holidays, in order to do beta testing ... and no, I'm not serious ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Plan for feature freeze?
On Fri, 30 Apr 2004, Joshua D. Drake wrote: Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. We could go for September 1st, which would mean most are back from holidays, in order to do beta testing ... and no, I'm not serious ... Why not? Seemed like a fairly good argument both yours and mine ;) To me, it ranks up there with lets freeze someday in the future ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] ecpg and the timezone database
Andrew Dunstan wrote: Bruce Momjian said: Does ecpg need to use the same timezone database as the backend? I just committed code so it will not, but I am not sure. surely all clients should be utterly ignorant of what the backend uses? OK, just asking the question to be sure. I was a little concerned that ecpg would be looking at some binary data from the backend and trying to do some timezone comparison on it. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(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 cleanly
Re: [HACKERS] Plan for feature freeze?
Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. We could go for September 1st, which would mean most are back from holidays, in order to do beta testing ... and no, I'm not serious ... Why not? Seemed like a fairly good argument both yours and mine ;) To me, it ranks up there with lets freeze someday in the future ... For me even September 1st does not seem too late. Major version up bring users pains including backup/restore application imcompatibilty... IMO to justify those pains we need to give users major enhancements. Honestly I don't understand why we should rush the major version up. -- Tatsuo Ishii ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] pg ANY/SOME ambiguity wrt sql standard?
Fabien COELHO [EMAIL PROTECTED] writes: As a temporary fix, what about _ANY and _SOME as aggregate names? Ick :-(. The use of leading underscores is an ugly C-ism that we should not propagate into SQL names. How about bool_or() and bool_and()? Or at least something based on OR and AND? I don't find ANY/ALL to be particularly mnemonic for this usage anyway. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Plan for feature freeze?
For me even September 1st does not seem too late. Major version up bring users pains including backup/restore application imcompatibilty... IMO to justify those pains we need to give users major enhancements. Honestly I don't understand why we should rush the major version up. I agree with this point even though I suggested August 1st. 7.5 has some extremely ambitious plans, far greater than 7.3 or 7.4 implemented. A longer release cycle might be a good idea. My personal daemons on this are: Vacuum -- is the stuff Jan is working going to make a July 1st date? If not... 7.5 should push. Win32 -- if it won't make it, then 7.5 should push. PITR is nice but not as vital (IMHO) as the two above. Replication -- we have either via Replicator or Slony-I which is due in a month. Sincerely, Joshua D. Drake -- Tatsuo Ishii ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL ---(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 cleanly
Re: [HACKERS] pg ANY/SOME ambiguity wrt sql standard?
Tom Lane wrote: Fabien COELHO [EMAIL PROTECTED] writes: As a "temporary" fix, what about "_ANY" and "_SOME" as aggregate names? Ick :-(. The use of leading underscores is an ugly C-ism that we should not propagate into SQL names. I second this... the whole __ is hard to type and remember. Sincerely, Joshua D. Drake How about bool_or() and bool_and()? Or at least something based on OR and AND? I don't find ANY/ALL to be particularly mnemonic for this usage anyway. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL
Re: [HACKERS] Plan for feature freeze?
Maybe we should take a vote on the cuttoff date scheduling. Marc, is this something that can be voted on by the group? --- Tatsuo Ishii wrote: Why don't we just set a freeze of August 1st? Give everyone just a little extra time. No float. If it doesn't make it by August 1st, it doesn't make it. We could go for September 1st, which would mean most are back from holidays, in order to do beta testing ... and no, I'm not serious ... Why not? Seemed like a fairly good argument both yours and mine ;) To me, it ranks up there with lets freeze someday in the future ... For me even September 1st does not seem too late. Major version up bring users pains including backup/restore application imcompatibilty... IMO to justify those pains we need to give users major enhancements. Honestly I don't understand why we should rush the major version up. -- Tatsuo Ishii ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Weird prepared stmt behavior
Alvaro Herrera [EMAIL PROTECTED] writes: Is this expected? If so, why? I'd expect the prepared stmt to be deallocated. prepare.c probably should have provisions for rolling back its state to the start of a failed transaction ... but it doesn't. Before jumping into doing that, though, I'd want to have some discussions about the implications for the V3 protocol's notion of prepared statements. The protocol spec does not say anything that would suggest that prepared statements are lost on transaction rollback, and offhand it seems like they shouldn't be because the protocol is lower-level than transactions. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Plan for feature freeze?
On Fri, 30 Apr 2004, Bruce Momjian wrote: Maybe we should take a vote on the cuttoff date scheduling. Marc, is this something that can be voted on by the group? At this time, no ... in a months time, let's revisit it and see where the various things are sitting ... quite frankly, we've spent more time on this discussion that may even be warranted in a months time ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] Timezone library on Unix
I am getting farther with the timezone library on Unix. First, I realized that the share/timezone library doesn't have a localtime file by default, so the PostgreSQL server doesn't know the local timezone. I added that and got: test= select current_timestamp; timestamptz --- 2004-04-30 18:52:14.930852+00 (1 row) test= select timeofday(); timeofday - Fri Apr 30 22:52:17.686324 2004 EDT (1 row) (How are we going to deal with the missing localtime file?) It is obviously seeing my local timezone, but it doesn't know that it is +04. It is at least reading the right directory. To test, define USE_PGTZ in pg_config.h and set USE_PGTZ=yes in Makefile.global. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Current CVS tip segfaulting
Alvaro Herrera Munoz [EMAIL PROTECTED] writes: strace'ing the postmaster suggested me that the dbname string in utils/init/postinit.c, the InitPostgres function, is the culprit. In fact, if I apply the following patch to tcop/postgres.c the whole thing stops happening. else if (argc - optind == 1) ! dbname = argv[optind]; ... else if (argc - optind == 1) ! dbname = pstrdup(argv[optind]); Surely this is a red herring --- that code path does not even execute except in the case of a standalone backend. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Is there any method to keep table in memory at startup
Hi thanx and sorry that I asked such a simple question in postgres-hackers list but the complexity which i feel on that basis please allow me to explain my problem further. As i am working on sorting order , length and substring functions for Hindi text(Indian Language)... Here is the problem which i found in postgresql... after setting collating sequence in proper way(i.e. C) the order was on basis of unicode values...but in Hindi Language some of combined unicode values makes a single character similarly length is not appropriate for these reasons hence substring operations so i designed a customized data type called IndCharand operations on it in order by statement the only function called is indchar_lt(defined for operator).. Now please guide me where is starting(where i can open connection to database) and ending of my programI feel only in indchar_lt function which will be called many times in order by statement causing performance degradation..as i am not much experienced this assumption may be wrong... so my question remains as it is that is there any such thing which can be called at startup of psql.to make connection to database regards Vinay Andrew Hammond wrote: Vinay Jain wrote: Hi thank you for such a useful information... but actually in my case if i keep table in disk it significantly degrades performance and even for a table of 10 rows it takes 1-2 minutes I think u r not beliving it ! am i right for example I create a table in which i use my customized data type say student create table student (Name INDCHAR //INDCHAR is customized data type age integer); now i give query like this select * from student order by name; it will search for it's comparator operator () and related function... in that function there is one lookup table if that table is in memory no problem! (oh but it can't be) if it is in disk my program makes connection to database and execute query which is just a select statement on a simple where condition of equality. then closes connection There's your problem. Creating database connections is an expensive operation. They are not intended to be opened and closed often or quickly. Open your database connection at the beginning of your program, and close it at the end. You could also throw an index on the column you're using in your order by clause, but that won't make a difference until your table get a little bigger. Please take further questions of this nature to the pgsql-novice list. so every time less than operator() is called it does the same task.. what i feel in table of 10 rows how many times the operator will be called(NO idea but must be 10 times) is there any solution.. thanks in advance regards vinay ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
