[HACKERS] Open Sourcing pgManage
Hello, As Command Prompt is about to release it's Replication product we are open sourcing our pgManage. pgManage is similar to pgAdmin but as it is java based it is truly cross platform and should easily support most if not all of the community supported platforms. I thought that we might donate it to the project as a whole. What are people's thoughts on this? Yes it has a Java requirement but hey that is a lot easier than a GTK requirement to fullfill. My thought is that it could be included as pgAccess used to be. Sincerely, Joshua D. Drake -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Open Sourcing pgManage
Hello, If that is the case that is fine. I just wanted to throw it out there but doesn't that mean that psql would be separate as well? J Peter Eisentraut wrote: Joshua D. Drake writes: I thought that we might donate it to the project as a whole. What are people's thoughts on this? I think the decision has been made that no new client applications will be included with PostgreSQL. We will provide a server and let a happy bunch of client applications and libraries develop around it. That has worked out pretty well lately, I think. -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Open Sourcing pgManage
D'oh, just clued into the 'java' aspect ... Joshua, will this run as a JSP, remotely, through Jakarta-Tomcat? One of the limitations of pgAdmin, as far as I'm concerned, is the fact that you can run it remotely ... if you could run pgManage under something like Jakarta-Tomcat as a JSP, that would be *really* cool ... Hello, Well right now you can't but there is no reason why it couldn't as an applet with some work. J ---(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 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(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: [pgsql-www] [HACKERS] Changes to Contributor List
I think the Emeritus word might be too hard for non-native English speakers, and even for less educated English speakers. Isn't that an even better reason to use it? :) My personal opinion would be that they can use dictionary.com if they don't know what it means. Chris ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] [pgsql-advocacy] Changes to Contributor List
Hello, My feeling is that advocacy should be just that: Advocacy. It doesn't matter who the intended audience is in reality. However, it is also important to remember that technical experts typically don't need to be sold on PostgreSQL. PHBs on the other hand probably do and thus much of our Advocacy work should be geared towards them. I believe one place where we are particularly week is PostgreSQL versus MySQL. We should have mountains of dead tree printables on why you should use PostgreSQL and why you shouldn't use mySQL. This can be done in a non-flammatory way. Sincerely, Joshua Drake Peter Eisentraut wrote: Josh Berkus writes: I was discussing specifically the Recognized Corporate Contributors which is, AFAIK, strictly a PHB thing, no? No. Please explain. I don't see anything in this project that should be strictly a PHB thing, the exception maybe being the weird whitepaper someone is going to write sometime. Anything else is intended for a greatly diverse audience, who may be engineers or decision makers, who may be technically incompetent, technically open-minded, or technical experts, and who may or may not have varying degrees of clues about open source, databases, and PostgreSQL. In other words, the general public. If you disagree, then maybe we should split up into advocacy-for-phbs and advocacy-for-real-people groups. Moreover, you seem to imply that the list of companies should primarily be a marketing instrument of the PostgreSQL project for attracting new users. I don't understand that. I would understand it if the list contained a large number of big names, but it does not, and it is not set up to strive for that goal. Right now, the list is nothing more than a marketing tool for the listed companies for attracting existing users to them. I think that list is a pretty dumb idea in the first place. We have a list of developers with company names next to them. Let readers make their own recognition evaluation. -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] [pgsql-advocacy] Changes to Contributor List
Andrew Sullivan wrote: On Thu, Nov 06, 2003 at 09:08:57PM +0100, Peter Eisentraut wrote: I think that list is a pretty dumb idea in the first place. We have a list of developers with company names next to them. Let readers make their own recognition evaluation. Your assuming that people are intelligent. In general they are not. In general people want to see that Cisco, Afilias, RedHat, ACS etc... use PostgreSQL. They want graphics, they want teddy bears. J I'm not sure that's all it's for. Every time we talk about using Postgres, people want to know who else uses it. It's really strange, but for some reason, people seem to believe that a product isn't any good unless a large number of people are already using it, and that it _is_ good if a large number of people do use it. (I guess the idea is that all those Windows users can't be wrong. Oh, wait. . .) A -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(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] [CORE] 7.4RC2 regression failur and not running stats
I can fire up our solaris machine and let you have access to it if you
want to do some destructive testing.
Tom Lane wrote:
Christopher Browne [EMAIL PROTECTED] writes:
For what it's worth, I have been running regression on Solaris with
numerous of the betas, and RC1 and [just now] RC2, with NO problems.
It seems clear that some Solaris installations are affected and some
are not. Presumably there is some version difference or some local
configuration difference ... but since we don't know what the critical
factor is, we have no basis for guessing what fraction of Solaris
installations will see the problem.
(And in that case, I would be quick to test the patch to ensure it
causes no adverse side-effects.)
Here is the proposed patch --- please test it ASAP if you can.
This is against RC2.
regards, tom lane
*** src/backend/postmaster/pgstat.c.orig Fri Nov 7 16:55:50 2003
--- src/backend/postmaster/pgstat.c Fri Nov 14 15:02:14 2003
***
*** 203,208
--- 203,216
goto startup_failed;
}
+ /*
+ * On some platforms, getaddrinfo_all() may return multiple addresses
+ * only one of which will actually work (eg, both IPv6 and IPv4 addresses
+ * when kernel will reject IPv6). Worse, the failure may occur at the
+ * bind() or perhaps even connect() stage. So we must loop through the
+ * results till we find a working combination. We will generate LOG
+ * messages, but no error, for bogus combinations.
+ */
for (addr = addrs; addr; addr = addr-ai_next)
{
#ifdef HAVE_UNIX_SOCKETS
***
*** 210,262
if (addr-ai_family == AF_UNIX)
continue;
#endif
! if ((pgStatSock = socket(addr-ai_family, SOCK_DGRAM, 0)) = 0)
! break;
! }
! if (!addr || pgStatSock 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not create socket for statistics collector: %m)));
! goto startup_failed;
! }
! /*
! * Bind it to a kernel assigned port on localhost and get the assigned
! * port via getsockname().
! */
! if (bind(pgStatSock, addr-ai_addr, addr-ai_addrlen) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not bind socket for statistics collector: %m)));
! goto startup_failed;
! }
! freeaddrinfo_all(hints.ai_family, addrs);
! addrs = NULL;
! alen = sizeof(pgStatAddr);
! if (getsockname(pgStatSock, (struct sockaddr *) pgStatAddr, alen) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not get address of socket for statistics collector: %m)));
! goto startup_failed;
}
! /*
! * Connect the socket to its own address. This saves a few cycles by
! * not having to respecify the target address on every send. This also
! * provides a kernel-level check that only packets from this same
! * address will be received.
! */
! if (connect(pgStatSock, (struct sockaddr *) pgStatAddr, alen) 0)
{
ereport(LOG,
(errcode_for_socket_access(),
! errmsg(could not connect socket for statistics collector: %m)));
goto startup_failed;
}
--- 218,285
if (addr-ai_family == AF_UNIX)
continue;
#endif
! /*
! * Create the socket.
! */
! if ((pgStatSock = socket(addr-ai_family, SOCK_DGRAM, 0)) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not create socket for statistics collector: %m)));
! continue;
! }
! /*
! * Bind it to a kernel assigned port on localhost and get the assigned
! * port via getsockname().
! */
! if (bind(pgStatSock, addr-ai_addr, addr-ai_addrlen) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not bind socket for statistics collector: %m)));
! closesocket(pgStatSock);
! pgStatSock = -1;
! continue;
! }
! alen = sizeof(pgStatAddr);
! if (getsockname(pgStatSock, (struct sockaddr *) pgStatAddr, alen) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not get address of socket for statistics collector: %m)));
! closesocket(pgStatSock);
! pgStatSock = -1;
! continue;
! }
! /*
! * Connect the socket to its own address. This saves a few cycles by
! * not having to respecify the target address on every send. This also
! * provides a kernel-level check that only packets from this same
! * address will be received.
! */
! if (connect(pgStatSock, (struct sockaddr *) pgStatAddr, alen) 0)
! {
! ereport(LOG,
! (errcode_for_socket_access(),
! errmsg(could not connect socket for statistics collector: %m)));
! closesocket(pgStatSock);
! pgStatSock = -1;
! continue;
! }
! /* If we get here, we have a working socket */
! break;
}
! /* Did we find a working address? */
! if (!addr || pgStatSock 0)
{
ereport(LOG,
(errcode_for_socket_access(),
! errmsg(disabling statistics collector for
Re: [HACKERS] [pgsql-advocacy] Not 7.5, but 8.0 ?
Hello, If Win32 actually makes it into 7.5 then yes I believe 8.0 would be appropriate. Sincerely, Joshua D. Drake On Mon, 17 Nov 2003, Josh Berkus wrote: Folks, Of course, while I was editing press releases at 2am, I started thinking about our next version. It seems certain that the next release, in 6-9 months, will have at a minimum the Windows port and ARC, if not Slony-I as well. Given all that, don't people think it's time to jump to 8.0?Seems like even 7.4 is hardly recognizable as the same database as 7.0. I'm posting this to both Advocacy and Hackers because I think that some people will have rather different points of view on the issue. But I wanted to start a discussion early this time. No flamewars, please! We all want PostgreSQL to be the best possible database. -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(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] Not 7.5, but 8.0 ?
As has been said before, many people think that a Windows port is the least interesting feature ever to happen to PostgreSQL, so you're going to Yes but these are people running Unix/Linux/BSD not Windows ;) have to come up with better reasons. Also note that most major number changes in the past weren't because the features were cool, but because the project has moved to a new phase. I don't see any such move happening. -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(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] Release cycle length
Hello, Personally I am for long release cycles, at least for major releases. In fact as of 7.4 I think there should possibly be a slow down in releases with more incremental releases (minor releases) throughout the year. People are running their companies and lives off of PostgreSQL, they should be able to rely on a specific feature set, and support from the community for longer. Sincerely, Joshua Drake Peter Eisentraut wrote: Neil Conway writes: Peter Eisentraut [EMAIL PROTECTED] writes: The time from release 7.3 to release 7.4 was 355 days, an all-time high. We really need to shorten that. Why is that? First, if you develop something today, the first time users would realistically get a hand at it would be January 2005. Do you want that? Don't you want people to use your code? We fix problems, but people must wait a year for the fix? Second, the longer a release cycle, the more problems amass. People just forget what they were doing in the beginning, no one is around to fix the problems introduced earlier, no one remembers anything when it comes time to write release notes. The longer you develop, the more parallel efforts are underway, and it becomes impossible to synchronize them to a release date. People are not encouraged to provide small, well-thought-out, modular improvements. Instead, they break everything open and worry about it later. At the end, it's always a rush to close these holes. Altogether, it's a loss for both developers and users. -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Commercial binary support?
Hello, I think what the person is looking for is: COMPANY PostgreSQL for Red Hat Enterprise 3.0. They probably have some commercial mandate that says that they have to have a commercial company backing the product itself. This doesn't work for most PostgreSQL companies because they back the Open Source version of PostgreSQL. Where someone like Command Prompt, although we happily support the Open Source version, we also sell Command Prompt PostgreSQL. It is purely a business thing, liability and the like. Sincerely, Joshua Drake Nigel J. Andrews wrote: On Wed, 19 Nov 2003, Bruce Momjian wrote: Marc G. Fournier wrote: On Wed, 19 Nov 2003, Michael Meskes wrote: On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote: I've been looking all over but I can't seem to see a company that is providing *up-to-date* postgresql support and provides their own supported binaries. Am I barking up the wrong tree entirely here? Why do you insist on their own binaries? I think there are several companies out there providing support for a given version of PostgreSQL and doubt they all ask for their own binaries. At least we do not. We don't either, nor do we worry about specific platforms ... And I know CommandPrompt doesn't care either. I don't even know what it means. If I were to build the 7.4 source, install it somewhere, tarball it up would that then count as providing our own supported binaries (assuming the support service is also offered of course)? Surely it's fairly common for someone to sell support and be happy to include the service of supplying the binaries so if requested, what's so special about it? Nigel Andrews ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Commercial binary support?
Hello Tell me if I am significantly wrong but Command Prompt PostgreSQL is nothing more than Open Source PostgreSQL including some application server stuff, some propriertary PL/Perl || PL/PHP and not much more. Ahh no. First our PL/Perl and PL/PHP is not propiertary in any way. It is open source, you are free to download it and use it at your leisure. Second we have better SSL support (although this is fixed in the current cvs for 7.3 series) Third we have compression over the connection stream for more efficient connectivity over congested networks. Also: Included graphical management tools (also now open source, pgManage) Modified shared memory management for better performance A policy of a minimum of 2005 before we won't support PostgreSQL. 24 hour / 7 day support with a history of performance for the customer. Oh... and: Native, built in as part of the database replication. Can you tell me a reason why somebody should use a closed source version of an Open Source product unless it contains some really significant improvement (say native Win32 or something like that)? See above. Can you tell me ONE reason why this does not work for other PostgreSQL companies such as `eval LONG LIST`? Personally I think everybody can have its business strategy but what REALLY sets me up is that this mail seems to mean that Command Prompt is the only support company around which is actually WRONG! No... not at all, nor was that my intent. There are many good PostgreSQL support companies. PgSQL, Inc. and Aglios come to mind. I was just trying to provide an example of what that particular company might be looking for. I wasn't even saying that we were the right company for them. I was just saying what I thought they were looking for. In my opinion everybody who has enough skills can do this kind of job. Being a support company has nothing to do with making a good Open Source product a closed source product. In my opinion giving something a new name and hiding away some code does not mean commercial backing and it does not mean being the god of all support companies. What in the world brought this on? I wasn't suggesting any of this. I was just trying to help clarify the guys statement. He couldn't have been talking about Red Hat for all I care. Sincerely, Joshua D. Drake Regards, Hans -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] RPM building fun
Is there some way to remove this piece of sh^H^Hlegacy from the configure script? Does anybody actually use info? All of GNU. Cheers, D -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 4 Clause license?
Based on the below wouldn't they also have to go after Microsoft? Marc G. Fournier wrote: On Thu, 20 Nov 2003, Andrew Dunstan wrote: trollOf course, now that SCO is claiming ownership of BSD code . /troll Interesting thread that ... last I read on the FreeBSD lists was speculation that they would be going after ppl like Cisco (re: TCP/IP Networking Code) since there really is nobody else large enough to bother with ... its going to be interesting to see :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(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 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] 4 Clause license?
Hello, My understanding is that they use the BSD stack (at least as the basis) for TCP/IP. Windows that is. J Marc G. Fournier wrote: On Thu, 20 Nov 2003, Joshua D. Drake wrote: Based on the below wouldn't they also have to go after Microsoft? Depends ... does MicroSoft use BSD TCP/IP, or did they write their own? I know that Linux is not using BSD TCP/IP (or, at least, they didn't in their first 3 incarnations of the stack) ... Marc G. Fournier wrote: On Thu, 20 Nov 2003, Andrew Dunstan wrote: trollOf course, now that SCO is claiming ownership of BSD code . /troll Interesting thread that ... last I read on the FreeBSD lists was speculation that they would be going after ppl like Cisco (re: TCP/IP Networking Code) since there really is nobody else large enough to bother with ... its going to be interesting to see :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(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 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org 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-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Commercial binary support?
Does that mean I have supplied Logictree Systems PostgreSQL? PostgreSQL with Logictree Systems TSearch2? Actually to some degree, yes. Of course a lot would depend on the type of contract you have with them you may be responsible for that code. However, I would love to see those patches. Sincerely, Joshua Drake And if I'd made no modifications to the code? I suppose I could have insisted that a separate contract be taken for the supply and support on top of the app. development contract. In fact, having written that I'm starting to think that should be the case. It is purely a business thing, liability and the like. Sincerely, Joshua Drake Nigel J. Andrews wrote: On Wed, 19 Nov 2003, Bruce Momjian wrote: Marc G. Fournier wrote: On Wed, 19 Nov 2003, Michael Meskes wrote: On Tue, Nov 18, 2003 at 04:19:35PM -0600, Austin Gonyou wrote: I've been looking all over but I can't seem to see a company that is providing *up-to-date* postgresql support and provides their own supported binaries. Am I barking up the wrong tree entirely here? Why do you insist on their own binaries? I think there are several companies out there providing support for a given version of PostgreSQL and doubt they all ask for their own binaries. At least we do not. We don't either, nor do we worry about specific platforms ... And I know CommandPrompt doesn't care either. I don't even know what it means. If I were to build the 7.4 source, install it somewhere, tarball it up would that then count as providing our own supported binaries (assuming the support service is also offered of course)? Surely it's fairly common for someone to sell support and be happy to include the service of supplying the binaries so if requested, what's so special about it? -- Nigel Andrews -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Limiting factors of pg_largeobject
Breaking all the client-visible LO APIs, for one thing ... Erck. 1. A larger identifier 2. An identifier that is not typed to the underlying system (oid) 3. The ability to be indexed We may benefit. Am I on crack? I don't see what you're getting at with #2 and #3 at all. OID is perfectly indexable. Well number 2 is that we have a limit on total number of OID's yes? Which means we could theorectically run out of OID's because of pg_largeobject. The ability to be indexed is obviously there but one problem we have is that you can't create an index on a system table at least not a user level index. Is there system level indexes that I am unaware of? As for #1, it'd theoretically be useful, but I'm not sure about the real-world usefulness. If your large objects are even moderately large (for whatever value of large applies this week), you're not likely to be expecting to cram 4 billion of them into your database. If we were doing LOs over for some reason it might be interesting to consider this, but I think they're largely a legacy feature at this point, and not worth that kind of effort. It would be better to put the development effort on creating serial access capability to toasted fields, whereupon LOs would really be obsolete. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Limiting factors of pg_largeobject
pg_largeobject already has an index (which is used by all the LO operations). Again, don't see what the width of the object ID column has to do with it. I was more after the not having an OID than the width of the ID column. regards, tom lane ---(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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Limiting factors of pg_largeobject
We're still at cross-purposes then. pg_largeobject doesn't have OIDs (in the sense of per-row OIDs). What I thought you were complaining about was the chosen datatype of the LO identifier column (loid), which happens to be OID. O.k. that was my main concern, which per your statement is unfounded ;). If I don't have to worry about it, then that solves the issue :) regards, tom lane -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(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] rebuilding rpm for RH9 error
I seen that the configure is done with: --with-krb5=/usr. make sure that you have krb5-devel installed. I also try to install the RPM already builded but I obtain: file /usr/include/sqltypes.h from install of postgresql-devel-7.4-0.5PGDG conflicts with file from package unixODBC-devel-2.2.3-6 Regards Gaetano Mendola ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] PostgreSQL port to pure Java?
Hello, All due respect but this seems like a completely insane idea. Sincerely, Joshua Drake Ivelin Ivanov wrote: Has this subject been discussed before? I did not find any references to it in the archives. I think that a co-bundle between an open source J2EE container like JBoss and a scalable database like PostgreSQL will be a blast. There are several well performing comercial Java dbs out there and there is Hypersonic which is free and fast, but supports only READ_UNCOMMITED and is build to grow up to ~200MB. Ivelin ---(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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Proposed Query Planner TODO items
I'm not going to be able to set this up. I just had to put my server into cold storage due to dismantling my office, and running the TPC stuff on my laptop is a joke. I'll contact the OSDL folks to see if they can run it. We can... depending on what you need for a server. J -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Issue with Linux+Pentium SMP Context Switching
Two suggestions.. 1. Patch linux kernel for HT aware scheduler. 2. Try running Xeons in HTdisabled modes. See if that helps. I would say using 2.6 on it is recommended anyways.. If possible of course.. I would avoid 2.6 on a production machine. 2.6 breaks alot (not as in a bad thing, but as in not really compatible with) of things. Wait until distribution vendors are shipping production with it. Sincerely, Joshua Drake Shridhar ---(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-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
Re: [HACKERS] [pgsql-advocacy] PostgreSQL speakers needed for OSCON 2004
Would this be at all useful? Someone mentioned that the 'fees' were relatively high though ... that you lose a fair amount off the top *to* Sourceforge? If we were going to do this, I would suggest just going right through paypal. Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(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-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
Re: [HACKERS] [pgsql-advocacy] PostgreSQL speakers needed for OSCON 2004
I'd rather pay the high fees and actually have access to the money ... Paypal I'm 110% *against* ... they have had *way* too many problems. In fact, there was a time when we ourselves setup the whole paypal account and were looking at moving to it, until our clients started telling us they wouldn't use it. We, as a business, have had something like 25 new clients sign up in the past month that its turning out are cards stolen from clients who made purchases through paypal in the recent past ... All due respect but that is just bad mojo in general. We have had zero problems with paypal. We also don't use them as our primary payment. We use a real merchant account and checking account for that. However paypal is good for a lot of things. Namely you want to provide the most ways to get paid (perfect for donations). It has also greatly increased its security and viability sense that really big billion dollar company call E-bay bought it. We (ie. Hub) just went through re-evaluating our online credit card services, and are currently in the middle of moving our accounts to a company called PaySystems (http://www.paysystems.com) that we've found to We use Echo, which also accepts electronic check but remember we are talking about donations here, not a for profit accepting credit cards. Sincerely, Joshua D. Drake have some of the better fees, and have yet to any major complaints about their services ... we haven't found any major complaints about our current one, but we just find we're losing too much money in the way of fees ... 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(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] PostgreSQL port to pure Java?
Jean-Michel POURE wrote: Le Mardi 09 Décembre 2003 16:15, Ivelin Ivanov a écrit : I think that a co-bundle between an open source J2EE container like JBoss and a scalable database like PostgreSQL will be a blast. Why not cut all trees on earth and replace them with plastic? Before that, we need to port mankind DNA to Windows 3.1 in order to improve speed. That seems a bit harsh. Personally I think porting PostgreSQL to java is silly but there is some argument to the benefit from his idea. If you are a java programmer. Sincerely, Joshua Drake ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL][ADMIN][HACKERS]data fragmentation
Hello, An quicker option would be to use rsync (on a stopped database of course). You can rsync to a new directory (off the filesystem) and then reformat the data filesystem and move it back. J Somasekhar Bangalore wrote: Hi, I too had the same problem; There was one query which used to take a very long time. What I did was, I took a backup of the whole database. Reinstalled postgres on a different mount point and restored the data back into the new database. Now my queries are running faster. Try it. All the very best. Somasekhar -Original Message- From: Jaime Casanova [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 3:07 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [GENERAL][ADMIN][HACKERS]data fragmentation Hi, i have a theorical question. i was thought that data fragmentation can cause a loss of performance when retrieving data from a database. Some DBMS solved this with dbspaces, but postgresql doesn't support this concept. so, pgsql databases tend to suffer from data fragmentation? if yes, what is the solution you recommend? also i was thought that even when DBMS support dbspaces DELETEing records may cause data fragmentation anyway. so, can i think of DELETE statement as a double-edged sword? it is indifferent in pgsql - it doesn't support dbspaces anyway? thanks in advance, Jaime Casanova (el_vigia) _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC Postgresql support, programming, shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] connections problem
hi i need to connect to by my database more then 100 connections, but after ~20-30 conn, postmaster says me Resource temporarily unavailable, what are this resource ? We need more info. What does your postgresql.conf say about max_connections? How much ram do you have? How much shared memory have you allocated? Sincerely, Joshua D. Drake im using debain with kernel 2.4.23-pre7, on P4 , (postgres 7.4.1) what can be wrong ? ---(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 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC Postgresql support, programming, shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com ---(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] connections problem
Hello, Perhaps you have too many open files? What else is running on this machine? Sincerely, Joshua D. Drake ivan wrote: max_connections=200 shared_buffers=2000 ram = 500M + 300M swap hdd = infinite On Fri, 26 Dec 2003, Joshua D. Drake wrote: hi i need to connect to by my database more then 100 connections, but after ~20-30 conn, postmaster says me Resource temporarily unavailable, what are this resource ? We need more info. What does your postgresql.conf say about max_connections? How much ram do you have? How much shared memory have you allocated? Sincerely, Joshua D. Drake im using debain with kernel 2.4.23-pre7, on P4 , (postgres 7.4.1) what can be wrong ? ---(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 -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC Postgresql support, programming, shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC - S/JDBC Postgresql support, programming, shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Remote Procedures
A E wrote: Hi, I was wondering is there or will there be support for remote procedures/functions in Postgresql? Not only server to server, but database to database? Such as calling a function in DB B from DB A or Server Gaia DB B from Server Zeus DB A? You could use dblink from contrib. Sincerely, Joshua D. Drake Alex -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Old binary packages.
Lamar Owen wrote: I am looking at the possibility of cleaning up the binary tree on the ftp site, and was wondering what the group thought about purging old binaries. What I was thinking would be to remove all but the last minor release of each major version. Thus, I would remove 7.4, but leave 7.4.1. The space taken by binaries is significant (about 1GB at this point). Since we are keeping all source releases (although I would question that, since we use CVS), keeping all the binaries around is just a space waster, IMHO. I would keep 7.3.5, 7.4, 7.4.1 (as 7.4 is the current release) and then do as you suggest for the older binaries. J Comments? -- 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 Mammoth PostgreSQL Replicator. Integrated 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] Allow backend to output result sets in XML
Greg Stark wrote: Tom Lane [EMAIL PROTECTED] writes: Brian Moore [EMAIL PROTECTED] writes: i would like to begin work on the TODO item Allow backend to output result sets in XML I am not sure why it's phrased that way --- surely the code to hack on is the client side, not the backend. Otherwise you need a protocol revision to make this happen, which implies hacking *both* ends. Presumably libpq would continue to use the binary protocol, but other clients could bypass libpq and just stream ascii xml queries. I would think that you would still use libpq with the binary protocol that understood an xml header request of some sort?? J Personally I don't see any point in xml, but if there was a standard query protocol then a client could send queries to any database that supported it without using any libraries. That might be useful. Of course you could do that without xml, but people seem to get more excited about complying with standards when they invoke xml. psql already has some code to output results as HTML tables; I'd think adding functionality in that vicinity would be the way to go. That could also be useful, mainly in that it could include the data from the query, as well as some meta data. Allowing import tools for programs like spreadsheets to do more intelligent things with the data than currently. -- 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
[HACKERS] pl/pgSQL versus pl/Python
Hello, With the new preload option is there any benefit/drawback to using pl/Python versus pl/pgSQL? And no... I don't care that pl/Python is now considered untrusted. Sincerely, Joshua D. Drake -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] ALTER SEQUENCE: Missing feature?
Sequences are tables in some very real senses. I don't see the value in duplicating code just to allow people to spell TABLE as SEQUENCE in these commands... I guess it comes down to a philosophical thing. Should people need to know the PostgreSQL internals like the fact that a SEQUENCE is currently implemented as a TABLE, or should they just be able to do reasonable things like call ALTER SEQUENCE when they alter a sequence? I would have to second this. From a user, user space programmer, dba perspective a SEQUENCE is a SEQUENCE not a table... thus operations such as ALTER that effect the SEQUENCE should use ALTER SEQUENCE. Sincerely, Joshua D. Drake Cheers, D -- 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] Preventing duplicate vacuums?
What about a situation where someone would have lazy vacuums cron'd and it takes longer to complete the vacuum than the interval between vacuums. You could wind up with an ever increasing queue of vacuums. Erroring out with a vacuum already in progress might be useful. I have seen this many times with customers as their traffic on the database grows. A simple check would be of great, great use. Sincerely, Joshua D. Drake ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Cannot read block error.
Hello, When was the last time you ran a reindex? Or a vacuum / vacuum full? Sincerely, Joshua D. Drake On Sat, 14 Feb 2004, Jason Essington wrote: I am running PostgreSQL 7.3.3 on OS X Server 10.2 The database has been running just fine for quite some time now, but this morning it began pitching the error: ERROR: cannot read block 176 of tfxtrade_details: Numerical result out of range any time the table tfxtrade_details is accessed. A description of the table is at the end of this email I have a backup from last night, so I haven't lost much data (if any), but I am curious if there is a way to recover from this (beyond restoring from backup) and how I would go about figuring out what caused it to prevent it from happening again. I will keep a copy of the data directory if anyone wants me to do any analysis on it (I will need instructions). Any insights would be appreciated. Thanks Jason Essington [EMAIL PROTECTED] hedgehog=# \d tfxtrade_details Table public.tfxtrade_details Column | Type | Modifiers ---+--+--- rid | integer | not null clientid | integer | tradeid | integer | rollid| integer | rollpct | numeric(10,8)| expdetailid | integer | expid | integer | contractpct | numeric(10,8)| contractamt | numeric(18,2)| origpct | numeric(10,8)| origamt | numeric(18,2)| acctgperiod | integer | acctgperiodid | integer | editdate | timestamp with time zone | edituserid| character varying(48)| parentid | integer | entityid | integer | tradedate | date | maturitydate | date | strategyid| integer | currencyid| integer | Indexes: tfxtrade_details_pkey primary key btree (rid), tfxlinks_entityid_index btree (entityid), tfxlinks_expdetailid_index btree (expdetailid), tfxlinks_expid_index btree (expid), tfxlinks_mdate_index btree (maturitydate), tfxlinks_parentid_index btree (parentid), tfxlinks_strategy_index btree (strategyid), tfxlinks_tradeid_index btree (tradeid) Triggers: RI_ConstraintTrigger_30891, RI_ConstraintTrigger_30894, tfxdetail_delete_trigger ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(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] Cannot read block error.
Hello, There are a couple of things it could be. I would suggest that you take down the database, start it up with -P? (I think it is -o '-P' it might be -p '-O' I don't recall) and try and reindex the database itself. You can also do a vacuuum verbose and see if you get some more errors you may have a corrupt system index that needs to be reindexed. Sincerely, Johsua D. Drake On Sat, 14 Feb 2004, Jason Essington wrote: Both vacuum [full] and reindex fail with that same error. vacuum is run regularly via a cron job. -jason On Feb 14, 2004, at 2:29 PM, Joshua D. Drake wrote: Hello, When was the last time you ran a reindex? Or a vacuum / vacuum full? Sincerely, Joshua D. Drake On Sat, 14 Feb 2004, Jason Essington wrote: I am running PostgreSQL 7.3.3 on OS X Server 10.2 The database has been running just fine for quite some time now, but this morning it began pitching the error: ERROR: cannot read block 176 of tfxtrade_details: Numerical result out of range any time the table tfxtrade_details is accessed. A description of the table is at the end of this email I have a backup from last night, so I haven't lost much data (if any), but I am curious if there is a way to recover from this (beyond restoring from backup) and how I would go about figuring out what caused it to prevent it from happening again. I will keep a copy of the data directory if anyone wants me to do any analysis on it (I will need instructions). Any insights would be appreciated. Thanks Jason Essington [EMAIL PROTECTED] hedgehog=# \d tfxtrade_details Table public.tfxtrade_details Column | Type | Modifiers ---+--+--- rid | integer | not null clientid | integer | tradeid | integer | rollid| integer | rollpct | numeric(10,8)| expdetailid | integer | expid | integer | contractpct | numeric(10,8)| contractamt | numeric(18,2)| origpct | numeric(10,8)| origamt | numeric(18,2)| acctgperiod | integer | acctgperiodid | integer | editdate | timestamp with time zone | edituserid| character varying(48)| parentid | integer | entityid | integer | tradedate | date | maturitydate | date | strategyid| integer | currencyid| integer | Indexes: tfxtrade_details_pkey primary key btree (rid), tfxlinks_entityid_index btree (entityid), tfxlinks_expdetailid_index btree (expdetailid), tfxlinks_expid_index btree (expid), tfxlinks_mdate_index btree (maturitydate), tfxlinks_parentid_index btree (parentid), tfxlinks_strategy_index btree (strategyid), tfxlinks_tradeid_index btree (tradeid) Triggers: RI_ConstraintTrigger_30891, RI_ConstraintTrigger_30894, tfxdetail_delete_trigger ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] friday 13 bug?
Hello, I personally ran into the exact same thing with another customer. They are running RedHat 8.0 with (2.4.20 at the time). We had to upgrade them to 2.4.23 and reboot. Worked like a charm. This was about two months ago. I swear it was almost the exact same error. Sincerely, Joshua D. Drake On Sat, 14 Feb 2004, zohn_ming wu wrote: Kernel 2.4.23 on redhat 8.0Please cc any response from linux kernel list. TIA. On or about 7:50am Friday 13 2004 my postgresql server breaks down. I can ssh and use top and ps but postgresql stops accepting connection. A small perl script that logs system load average also hangs. I cannot kill -9 any hang processes including postgreqsql postmaster process. I then check dmesg and found error message that I copy and paste at the bottom. I finally issued reboot but reboot also didn't work and I had to push the reset button. AMD XP 2500+ with 1.5GB Memory. Postgresql data lives on a software raid 1 device. Kernel 2.4.23 on redhat 8.0 Postgresql 7.4 The last time server was rebooted was about 60 days ago when I upgraded the kernel Can someone suggest anything to help me avoid this type of breakdown? I tried to post the message yesterday but postgresql list wasn't responding at all to subscription request. swap_free: Bad swap file entry 0004 kernel BUG at buffer.c:539! invalid operand: CPU:0 EIP:0010:[c0138e8e]Not tainted EFLAGS: 00010282 eax: cfd10a40 ebx: 0002 ecx: e75f6ac0 edx: c02c548c esi: e75f6ac0 edi: 0001 ebp: e75f6ac0 esp: f74efe60 ds: 0018 es: 0018 ss: 0018 Process postmaster (pid: 457, stackpage=f74ef000) Stack: 0002 c01397ab e75f6ac0 0002 e75f6ac0 1000 c013a326 e75f6ac0 1000 0042 c2166b40 f7822980 c013aaef f7822980 c2166b40 1000 c2166b40 f7822980 1000 f7822a34 c016064c Call Trace:[c01397ab] [c013a326] [c013aaef] [c016064c] [c0160310] [c012af71] [c012b4f6] [c015d8a9] [c0137753] [c010733f] Code: 0f 0b 1b 02 17 e0 23 c0 8b 02 85 c0 75 07 89 0a 89 49 24 8b [EMAIL PROTECTED]@[EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(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] log_line_info plan
Andrew Dunstan wrote: I am about to redo the patch that would allow tagging of log lines with info via a printf-style string. Current plans are to call the config parameter log_line_info and implement the following escapes: %U = user %D = database %T = timestamp %P = pid %L = session log line number %C = sessionid cookie (hex encoded session start time + pid) %S = session start timestamp %I = Command Tag (e.g. CREATE TABLE) Any comments or suggestions before I start? My be kind of cool if we a a duration variable in there, especially if combined with %I J 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 -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(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] Tablespaces
Is it possible to put WALs and CLOGs into different tablespaces? (maybe different RAID systems). Some companies want that ... You can do this now, but it would be nice to be able to have it actually configurable versus the hacked linked method. J -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgsql-www] [HACKERS] The Name Game: postgresql.net vs.
IMHO, the domain name isn't the make/break of whether going to GForge will succeed ... the success will be a matter of marketing it, and making sure that its project are well known ... personally, focusing on the domain is like focusing on the name of a car when you buy it, not on its features and/or price ... Really? What about BMW, Volvo or Mercedes? Sincerely, Joshua D. Drake 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 begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(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] Log rotation
Andrew Sullivan wrote: On Sat, Mar 13, 2004 at 10:45:35AM -0500, Rod Taylor wrote: Not that I'm volunteering, but I think the biggest issue is many users simply don't know how to approach the problem. Some docs on using syslog, cron, etc. with PostgreSQL to accomplish maintenace jobs would probably be enough. There is the basic problem that if you don't have root on your host, setting up syslog is one more thing you have to get the rootly ones to do. Some of them are, uh, challenged in that area. What a polite way to say that they have zero business logging in as root ;) A -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] COPY formatting
That is why I suggested providing a pre-written/pre-compiled/installed function for CSV (call it CSV?). Advanced users could still write their own as people can write many other things if they know their ways. As someone who just went through a whole truckload of crap getting delimited files parsed from MSSQL to PostgreSQL. I believe yes this would be great thing. We ended up using plPython with the CSV module. Sincerely, Joshua Drake ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] COPY formatting
And, BTW, I deal with CSV *all the time* for my insurance clients, and I can tell you that that format hasn't changed in 20 years. We can hard-code it if it's easier. Well many of my clients consider CSV Character Separated Value not Comma... Thus I get data like this: Hello,Good Bye Hello Good Bye Hello,Good Bye This, They're ThisThey're ThisIs A 1 Dealing with all of these different nuances is may or may not be beyond the scope of copy but it seems that it could be something that it can handle. Python has a csv module that allows you to assign dialects to any specific type of import you are performing. Sincerely, Joshua D. Drake -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] PostgreSQL ES3.0 problems?
: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: ProcessQuery
DEBUG: ProcessUtility
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: ProcessQuery
DEBUG: reaping dead processes
DEBUG: child process (pid 858) was terminated by signal 11
LOG: server process (pid 858) was terminated by signal 11
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing shared memory and
semaphores
DEBUG: shmem_exit(0)
DEBUG: invoking IpcMemoryCreate(size=36421632)
LOG: database system was interrupted at 2004-03-19 06:52:03 PST
LOG: checkpoint record is at 0/58E2B4F8
LOG: redo record is at 0/58E2B4F8; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 630; next oid: 217646
LOG: database system was not properly shut down; automatic recovery in
progress
FATAL: The database system is starting up
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: BackendStartup: forked pid=860 socket=8
DEBUG: reaping dead processes
DEBUG: child process (pid 860) exited with exit code 0
LOG: ReadRecord: record with zero length at 0/58E2B538
LOG: redo is not required
LOG: database system is ready
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: reaping dead processes
After chasing our tails a little bit we decided to test the community
PostgreSQL 7.3.6. We were able to produce similar results with
PostgreSQL 7.3.6. Again only in SMP mode, only on ES 3.0.
Similar problems occured when trying to do a select * from a large
table (about 2Gig in size with about 1.5 million rows). Here is a
strings from a core dump that is associated:
CORE
CORE
postmaster
postgres: postgres test [local] SELECT
CORE
postmaster
CORE
FLINUX
hat exists.
out of memory in PortalHashTable
trying to delete portal name that does not exist.
ltsWriteBlock: failed to write block %ld of temporary file
Perhaps out of disk space?
ltsReadBlock: failed to read block %ld of temporary file
LogicalTapeWrite: impossible state
LogicalTapeBackspace: unexpected end of tape
LogicalTapeSeek: unexpected end of tape
tuplesort_puttuple: invalid state
tuplesort_performsort: invalid state
tuplesort_gettuple: invalid state
tuplesort_gettuple: bogus tuple len in backward scan
tuplesort_rescan: invalid state
tuplesort_markpos: invalid state
tuplesort_restorepos: invalid state
tuplesort: unexpected end of tape
tuplesort: unexpected end of data
SelectSortFunction: cache lookup failed for operator %u
Cannot create unique index. Table contains non-unique values
copytup_datum() should not be called
tuplestore_puttuple: invalid state
tuplestore_donestoring: invalid state
tuplestore_donestoring: seek(0) failed
tuplestore_gettuple: invalid state
tuplestore_gettuple: bogus tuple len in backward scan
tuplestore_rescan: invalid state
tuplestore_rescan: seek(0) failed
tuplestore_markpos: invalid state
tuplestore_restorepos: invalid state
tuplestore: unexpected end of tape
tuplestore: unexpected end of data
CopyQuerySnapshot: no snapshot has been set
pg_char_to_encname_struct(): encoding name too long
UtfToLocal: could not convert UTF-8 (0x%04x). Ignored
LocalToUtf: could not convert (0x%04x) %s to UTF-8. Ignored
default conversion proc for %s to %s not found
default conversion proc %u for %s to %s not found in pg_proc
Invalid destination encoding name %s
Invalid source encoding name %s
SetDatabaseEncoding(): invalid database encoding
Invalid %s character sequence found (0x
Unicode = 0x1 is not supported
MbP?
@UU
A. K.
bool
bytea
char
name
int2
int2vector
int4
regproc
regclass
regtype
text
oidvector
smgr
_int4
_aclitem
ctid
xmin
cmin
xmax
cmax
tableoid
MbP?{
-infinity
abstime
acsst
*acst
aesst
I tried running the pg_dump in single proc mode and the machine ran just
fine. Once we put it in SMP mode and ran the dump again it trashed the
machine we had to reboot. Once we rebooted we forced an FSCK and then we
kernel panicked. We now have fairly extensive FS corruption ;)
Any thoughts?
Sincerely,
Joshua D. Drake
--
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
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
begin:vcard
fn:Joshua D. Drake
n:Drake;Joshua D.
org:Command Prompt, Inc.
adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA
email;internet:[EMAIL PROTECTED]
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0034
note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl.
x-mozilla-html:FALSE
url:http://www.commandprompt.com/
version:2.1
end:vcard
---(end
[HACKERS] Timeline for 7.4.3?
Hey, We have many machines that run Solaris. I know that there are patches out there for some of the bugs in 7.4.2 for Solaris but I was wondering what the timeline for an official 7.4.3 was? Sincerely, Joshua D. Drake -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] PostgreSQL 7.4.2 and Cygwin a no go?
Hello, We are able to compile without issue but it won't start. The exact same config works perfectly with 7.3.6. Here is the output: $ /usr/local/pgsql/bin/postmaster -D data DEBUG: /usr/local/pgsql/bin/postmaster: PostmasterMain: initial environ dump: DEBUG: - DEBUG: !::=::\ DEBUG: !C:=C:\cygwin\bin DEBUG: ALLUSERSPROFILE=C:\Documents and Settings\All Users DEBUG: APPDATA=C:\Documents and Settings\scf\Application Data DEBUG: CLIENTNAME=Console DEBUG: COMMONPROGRAMFILES=C:\Program Files\Common Files DEBUG: COMPUTERNAME=TRAUMA DEBUG: COMSPEC=C:\WINDOWS\system32\cmd.exe DEBUG: CVS_RSH=/bin/ssh DEBUG: HOME=/home/scf DEBUG: HOMEDRIVE=C: DEBUG: HOMEPATH=\Documents and Settings\scf DEBUG: HOSTNAME=trauma DEBUG: INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\ DEBUG: INFOPATH=/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info: DEBUG: LIB=C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\ DEBUG: LOGONSERVER=\\TRAUMA DEBUG: MAKE_MODE=unix DEBUG: MANPATH=/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man DEBUG: NUMBER_OF_PROCESSORS=1 DEBUG: OLDPWD=/home/scf DEBUG: OS=Windows_NT DEBUG: /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem DEBUG: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH DEBUG: PROCESSOR_ARCHITECTURE=x86 DEBUG: PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 1, AuthenticAMD DEBUG: PROCESSOR_LEVEL=6 DEBUG: PROCESSOR_REVISION=0801 DEBUG: PROGRAMFILES=C:\Program Files DEBUG: PROMPT=$P$G DEBUG: PS1=\[\033]0;[EMAIL PROTECTED] \[\033[33m\w\033[0m\]$ DEBUG: PWD=/home/scf/postgresql-7.4.2 DEBUG: SESSIONNAME=Console DEBUG: SHLVL=1 DEBUG: SYSTEMDRIVE=C: DEBUG: SYSTEMROOT=C:\WINDOWS DEBUG: TEMP=/cygdrive/c/DOCUME~1/scf/LOCALS~1/Temp DEBUG: TERM=cygwin DEBUG: TMP=/cygdrive/c/DOCUME~1/scf/LOCALS~1/Temp DEBUG: USER=scf DEBUG: USERDOMAIN=TRAUMA DEBUG: USERNAME=scf DEBUG: USERPROFILE=C:\Documents and Settings\scf DEBUG: VS71COMNTOOLS=C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\ DEBUG: _=/usr/local/pgsql/bin/postmaster DEBUG: TZ=FLEST-2FLEST-3,M3.5.0/3,M10.5.0/4 DEBUG: - DEBUG: found "/usr/local/pgsql/bin/postgres" using argv[0] DEBUG: invoking IpcMemoryCreate(size=10461184) Segmentation fault (core dumped) -- 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] pg_encoding not needed anymore
g a data store for many databases, not a single database. But I think it is far too sanctified by history to change now, just as Ken Thompson now wishes he had put an 'e' on the end of 'creat' but can't go back and fix it. Maybe we should think about a symlink/hardlink to use a better name. initcatalog? cheers andrew ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- 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 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] contrib vs. gborg/pgfoundry for replication solutions
Hello, My personal opinion is that contrib should be removed entirely. Just have a contrib.txt that says all contrib modules are at pgfoundry or whatever. Sincerely, Joshua D. Drake Jan Wieck wrote: Taking into account that quite a few people have repeatedly stated that the components in contrib are considered more supported/recommended than similar solutions found on gborg or any other external site, I suggest we move the projects dbmirror and dblink to gborg. The rserv contrib module seems to me to be an early Perl prototype of erserver, nobody is working on any more. I suggest we drop that entirely. Comments/alternatives? Jan ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] contrib vs. gborg/pgfoundry for replication solutions
tsearch, I believe, is maintained somewhere else already, no? same with tsearch2? Yes that is correct but I think they commit back to contrib before they release. Realistically, although I did not used to agree, I believe that the only that that should come with PostgreSQL is PostgreSQL and required items for PostgreSQL. IMHO: PostgreSQL should include: PostgreSQL Psql All development headers C/C++ Libs Everything else should be on SourceForge or Gforge or whatever. The possible exception would be the pl stuff. Sincerely, Joshua D. Drake Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] contrib vs. gborg/pgfoundry for replication solutions
Hello, Well perhaps we can have exceptions. TSearch would be a good exception as it really should be integrated into PostgreSQL anyway. There are very few of these that I think would be an issue. Sincerely, Joshua D. Drake Oleg Bartunov wrote: The problem with moving all contribs to gborg is that sometimes it's required to change many modules, for example, because of changing GiST interface. Tom saves a lot of working for contrib authors, when he change code in core. I'm not sure, gborg would provide easy access for such kind of things. tsearch2, particularly, is maintained in pgsql CVS. Oleg On Wed, 21 Apr 2004, Joshua D. Drake wrote: tsearch, I believe, is maintained somewhere else already, no? same with tsearch2? Yes that is correct but I think they commit back to contrib before they release. Realistically, although I did not used to agree, I believe that the only that that should come with PostgreSQL is PostgreSQL and required items for PostgreSQL. IMHO: PostgreSQL should include: PostgreSQL Psql All development headers C/C++ Libs Everything else should be on SourceForge or Gforge or whatever. The possible exception would be the pl stuff. Sincerely, Joshua D. Drake Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(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] contrib vs. gborg/pgfoundry for replication solutions
The thing is, for how many ppl are seperate packages difficult? I know for me, under FreeBSD, I cd to a /usr/ports/databases/pg_autovacuum and type 'make install' and its done ... I thought that stuff like Redhat had the full screen installer that lists things? Well, if setup correctly for redhat, debian or even SuSE you would type: apt-get install pg_autovacuum or with redhat you might also do yum install pg_autovacuum But that is packaging and that is up to the developers of the particular project. Joshua D. Drake My point is that all of this stuff shouldn't be in the core CVS ... its a packaging issue, not a cvs one ... 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] contrib vs. gborg/pgfoundry for replication solutions
Hello, I believe that one problem with the contrib is that in order to build most of the contrib modules you need the PostgreSQL source. That is silly. If I have PostgreSQL installed with all headers, I should be able to download a PostgreSQL project app (pgAdmin whatever) and just build it against PostgreSQL. Very few OSS projects are like that. If I want PHP I don't need Apache source, I just need the Apache development stuff (headers etc...). If we were to break out contrib so it was on its own, let people figure out their own build methods. You don't "have" to use autoconf (although it is a good idea). You don't NEED PostgreSQL source etc... Sincerely, Joshua D. Drake Marc G. Fournier wrote: On Wed, 21 Apr 2004, Rod Taylor wrote: We have the current issue of people not knowing that projects like pgadmin exist or where to find the jdbc drivers. Agreed ... but makign one big META package isn't going to fix that ... as someone else suggested, put a README file in the contrib directory that points ppl to projects.postgresql.org ... These basic components (and others a large segment uses that are well maintained) should go through a release cycle with the -core including the platform test/report phase and be prominently listed in the downloads area and documentation areas -- just as we do for PostgreSQL proper. *ack* ... now the beta cycle just quadrupled in length ... so we develop for 4 months, and beta for a year while we make sure everyone else's packages work with the -core? Most DBAs that I know will not upgrade based on a .0 release on a production system ... they will wait for at least a .1 release ... between .0 and .1 is when projects like PgAdmin should be doing their testing to make sure that they are good for the new major release ... Goto http://postgresql.org, now track down the jdbc drivers or how to use them. To a significant portion of our users this is more important than CREATE FUNCTION is and in 7.5 jdbc documentation will be much more difficult to find, but no less important than it used to be. Now, out of all of the PostgreSQL users, what % are using JDBC? What % are using ODBC? What percentage of those using JDBC are also using ODBC? What % of those using PgAdmin are also using ODBC? For that matter, how many ppl using JDBC only want to download the .jar file itself, and not the source code? % of Binary-Only PgAdmin users? ODBC driver? The point of projects.postgresql.org is that if someone *is* looking for an addon, they should be pointed to projects.postgresql.org ... if you try and merge everything into the -core distribution, you are either going to miss something that *someone* wants to use at some point, *or* one helluva large tar file to download ... 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] Usability, MySQL, Postgresql.org, gborg, contrib,
plpgsql is more close to postgres then plPython or plPerl, and after all is nearest SQL then plPtyhton or plPerl so a DBA find it more confortable then others languages. DBA probably... programmer? Doubtful. The majority of people that I run into that are using PostgreSQL are not DBA's. They are programmers trying to do it a better way. Providing plPerl or plPython etc... allows them to stay in a native and productive environment. Sincerely, Joshua D. Drake my two cents. Regards Gaetano Mendola ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
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] 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?
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] Usability, MySQL, Postgresql.org, gborg, contrib,
I know both. :-). Seriously - I'd like to raise my voice in favor of installing plpgsql in template1 by default. I haven't heard any good reason not to (nor even a bad reason). If we install plPGSQL by default, we should install any other pl language that was configured at runtime by default as well. This includes plPerl, plTCL, and plPython. Of course only if they were compiled in, but sense they are a part of the core distribution we shouldn't favor one over the other. Personally, plpgSQL is only useful to those who are coming from Oracle. People are more likely to be comfortable with plPython or plPerl than plpgSQL. Sincerely, Joshua D. Drake cheers andrew ---(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 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] [pgsql-advocacy] What can we learn from MySQL?
Does anyone know of an open source project that *has* successfully displaced a market of mature, established products WITHOUT a commercial entity providing marketing, support direction? gcc? Nope most big houses will use Intel/Borland/Vc++ or whatever comes with Solaris. In fact, I can not think of a single project that has displaced a commercial one, without market force behind it. Linux won't do it without RedHat/Novell. I would even dare say that Novell will be that driving force, not RedHat. Even Apache has an entity... It actually became much more popular once that entity came to existence (even though it was a 501). Another look at Linux shows that it's popularity amongst the washed masses didn't really soar until Big Blue (IBM) starting pushing it. PHP might be an interesting thought, but ASP is used more widely as is Java for commercial stuff. Sincerely, Joshua D. Drake ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] PostgreSQL pre-fork speedup
The fact that windows has a heavy process / lightweight thread design means little to me, since I'll likely never deploy a production postgresql server on it that needs to handle any serious load. Yes but Solaris also has a heavy process / lightweight thread design. J ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Call for 7.5 feature completion
Simon Riggs wrote: On Mon, 2004-05-17 at 15:10, Bruce Momjian wrote: It is too late to think about pushing back another month. We had this discussion already. June 1 is it. Just to throw in my .02, plPerlNG won't be ready for testing until mid, later June either. Then there is also plPHP which although we haven't had any bug reports still needs some more peer review. Also we would like to submit our ECPG which includes SET DESCRIPTOR and error handling but that too needs more peer review. It just seems, considering the current state of 7.4.2 (stable, just now being deployed in production shops) that we should make a longer development time for 7.5. Personally, Win32, subtransactions and PITR are what we are after. Second would be inclusion of plPHP and plPerlNG which are arguably the most widely used languages to connect to PostgreSQL. Sincerely, Joshua D. Drake -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for 7.5 feature completion
Mario Weilguni wrote: Interesting. We have made COMPLETELY different experiences. There is one question people ask me daily: When can we have sychronous replication and PITR?. Performance is not a problem here. People are more interested in stability and enterprise features such as those I have mentioned above. I doubt that. Having deployed several 7.4 databases, the first customers ask (of course not in technical speech, but in the meaning) when the problem with checkpoint hogging system down is solved. This is a really serious issue, especially when using drbd + ext3. ^^^ Well that seems to be part of the problem. ext3 does not scale well at all under load. You should probably upgrade to a better FS (like XFS). I am not saying that your point isn't valid (it is) but upgrading to a better FS will help you. Sincerely, Joshua D. Drake The system will become really unresponsive when checkpoint is running. I heavily await 7.5 because of the background writer. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for 7.5 feature completion
plPHP and plPerlNG both belong on pgfoundry, not in the core distribution ... Uhhh?? Are you ripping out all core pls then? plPerlNG is supposed to replace plPerl, I was talking with Bruce and he seemed to think that (as long as the code was good enough) that we could incorporate plPHP??? 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(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
The much I am for pulling stuff that does not belong into core, doing it just for the fun of cleaning up or trimming doesn't do. One of the major functions of CVS is that one can tag collections of revisions that together build a release, a known to be working snapshot of file revisions. If we completely lose the ability to tell what version of what PL, client interface or extension works with what version of the backend, we're losing some important detail here. Also, one of the best features of PostgreSQL is that you can, at will write a procedure in just about anything... It seems that keeping at least the most popular pl implementations would be an important step. ] Jan -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Call for 7.5 feature completion
I assume your ecpg will be a patch to the existing ecpg rather than a new verion, right? Yes it is a patch against 7.4.2 J -- 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] Call for 7.5 feature completion
Why is it our responsibility to ensure that though? Shouldn't the developer (or group of developers) responsible for the PL/interface/extension be responsible for that? Let's use plPHP as an example here ... I'm going to guess that it supports PHP4, which is the 'standard' right now ... what about PHP5? If not, what happens in 3 months if/when that support is added? Do ppl using PHP5 have to wait until the next release of PostgreSQL before they can use it? Actually this is a pretty good example. Yes right now it supports PHP4, it will support PHP5 when PHP5 is ready. And of course, no they would not have to wait. They could download and patch against the current source tree... The thing is, whether as part of core, or as a seperate project, *any* pl/interface/extension has to be maintained in order to be in sync ... if done as a seperate project, in parallel with core, it is at least possible to release on their own timelines in order to correct bugs, or add features ... as part of core, new features/bug fixes have to wait for all of core to be released ... Well actually no, because of the above mentioned. Even if plPHP is on pgFoundry... there is no reason why a README couldn't be included in the src/pl/plphp directory that says: look here for the latest release etc... Sincerely, Joshua D. Drake 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 -- 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 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
So, yea, I am frustrated. I know these features are hard and complex, but I want them for PostgreSQL, and I want them as soon as possible. I guess what really bugs me is that we are so close to having these few remaining big features, and because they are so complex, they are taking a lot longer to arrive than previous features, and sometimes see a year pass without progress on some items, and that bugs me. So why do we wait for some of these features? The bgwriter is done right? Why don't we backport to 7.4.x and release with 7.4.3? What about the vacuum stuff Jan was doing? I guess what I am saying is, what features are in HEAD that can be backported to 7.4.x without the requiring of an initdb? Yes it would be breaking from the tradition of very little feature releases in incrementals but then again maybe that would be a good thing... Sincerely, Joshua D. Drkae -- 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 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Call for 7.5 feature completion
a release, etc ... I'd almost say that time would be better spent on coming up with an effective upgrade method so that upgrading to new releases is easier ... Please note that I'm not against the backporting, but do understand the arguments against it in terms of time and manpower ... I believe they are valid arguments too and if we were to do it we would definately need to be selective about which features get back ported but forward movement can be in the present tree as well. 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 ---(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
Peter Eisentraut wrote: Joshua D. Drake wrote: Uhhh?? Are you ripping out all core pls then? plPerlNG is supposed to replace plPerl, I was talking with Bruce and he seemed to think that (as long as the code was good enough) that we could incorporate plPHP??? One reason against including plPHP in the core would be that it would create a circular build dependency between the packages postgresql and php. I think we should rather avoid that. It is no different that the dependency between plPerl and Perl, plPython and Python or worse plTCL and TCL (which typically isn't installed anymore). Sincerely, Joshua D. Drake -- 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] Call for 7.5 feature completion
Marc G. Fournier wrote: On Tue, 18 May 2004, Robert Treat wrote: Just like Bruce has often asked the community how they feel about him balancing his time between things like speaking engagements and patch applications, core developers have a limited amount of time they can spend on any given development effort. If I had to pick (If I got to pick?), I would rather see Bruce/Tom/Jan working on helping these guys finish PITR/WIN32/Tablespaces/etc... than working on closing the 7.5 branch. Except you miss one key point here ... if Bruce/Tom/Jan have that sort of time, why aren't they doing it now? Well I think you might of missed his point. His point was if he could pick their priorities. I would kind of agree with Robert except that there are other dynamics involved... Jan works for Afilias thus does what Afilias directs him to do and what that is right now is Slony-I. Tom works for RedHat but from what I can tell is basically a rogue agent ;). However if Tom stops works what he is doing to help with PITR etc... I think a lot of the innner world of PostgreSQL would simply stop (if I am wrong please correct me). Bruce --- well what can you say about Bruce ;). Seriously though, we all have the roles that we play. I don't think redirecting specific resources to other resources will help beyond slowing up the original resources. Sincerely, Joshua D. Drake 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 -- 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] Call for 7.5 feature completion
This is very much different, because the PHP distribution contains the PostgreSQL driver, whereas the other languages do not. So you would have PHP build depends on PostgreSQL Ahh I see your point, EXCEPT :) plPHP does not require PostgreSQL support to be built into PHP. Sincerely, Joshua D. Drake PostgreSQL build depends on PHP Not good. -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Call for 7.5 feature completion
That is irrelevant. A normal binary package of PHP does build the PostgreSQL support (which is surely in our interest), so the build dependency holds. Then I am afraid I don't understand the actual problem. plPHP does not create a circular dependency because it doesn't require PHP to have PostgreSQL support. Also PHP does not compile the PostgreSQL support by default. This is no different that Perl, which also has a PostgreSQL driver but plPerl does not require DBD::Pg to compile. Sincerely, Joshua D. Drake Sincerely, Joshua D. Drake PostgreSQL build depends on PHP Not good. -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Call for 7.5 feature completion
Peter Eisentraut wrote: Joshua D. Drake wrote: Of course not, but I still don't see your point. plPHP doesn't need PHP+PostgreSQL support. Nor does PHP+PostgreSQL conflict with using plPHP... PHP doesn't even need to be installed for plPHP to work... You just need the source tree for building. O.k. now I get it.. Basically you are saying that in order to build plPHP you need PHP and PostgreSQL (regardless if they know about each other). So in order to build plPHP you need to build PostgreSQL, then PHP, then plPHP... versus just Postgresql+plPHP... However plPHP is a configure option (when patched)... Thus if they choose with-php then they would (presumably) know what they were getting into. That makes sense. Sincerely, Joshua D. Drake I don't talk about manual build processes, I talk about (semi-)automatic package builds. The PHP package has a build dependency on PostgreSQL, because it needs libpq. So PostgreSQL needs to be built and installed before PHP can be built. But then, if PL/PHP were to be integrated into PostgreSQL, PHP needs to be installed first, so the PostgreSQL+PL/PHP build can get at the PHP headers files and whatever else it needs. So you can neither build PHP first nor build PostgreSQL first. So building PL/PHP doesn't need a PHP with PostgreSQL support. But no one is going to build two versions of PHP packages just so PostgreSQL can build. That is a mess we can happily avoid. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for 7.5 feature completion
So you then have to build PHP twice, in an RPM build environment. You mean I can't just have the headers installed to build plPHP? So, follow the No you need to make sure that PHP is available as a shared lib. 1.) Build PostgreSQL 2.) Build PHP (with PostgreSQL client support) 3.) Build plPHP (with PostgreSQL SPI support, or maybe even PostgreSQL client support for cross database queries? :-)) Right. Try building the RPMs for PHP plus PostgreSQL and plPHP, then tell me how you solved the circular dependency. Actually plPHP doesn't require the PostgreSQL source tree... you would just have to modify the Make file to point to the right places. J ---(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] Call for 7.5 feature completion
So, why tie it into the PostgreSQL source tree? Won't it be popular enough to live on its own, that it has to be distributed as part of the core? Honestly, I don't know if it would be popular enough on its own. Now the plPerlNG that Andrew and us are working, yes but plPHP? It is nifty, it is cool, it is very capable but it is still PHP. I think the point of having it in core is that the three most popular user space languages are: Python Perl PHP If those are covered within core under the pl* then we have all bases covered. I am not saying that it should be in core (although I definately think plPerlNG should be). This all started because it was suggested it could be :) J 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 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Call for 7.5 feature completion
Tatsuo Ishii wrote: At least in Japan PHP is much more popular than Python. If we have plpython in core, I see no reason we do not have plPHP in core at least from the "popularity" point of view. Well I don't know anywhere that PHP isn't more popular than Python. The question I think is a technical one. Python is a better "language" that PHP is. Perl is as well but that is a whole other argument. PHP is what I call the "Dumb Monkey" language. It isn't meant to be rude, but the reality is that almost any dumb monkey can code something in PHP. Python takes actual thought to produce something useful. Whether or not that is a bad thing is for another argument :) Sincerely, Joshua D. Drake -- Tatsuo Ishii ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- 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] Call for 7.5 feature completion
Amen. plperlNG was always intended as a replacement. In fact, one of the reasons I'm a bit sad about us rushing to feature freeze on 1 June is that Joshua and I had hoped to get a greatly beefed up plperl ready in time for 7.5, but I don't think we can make June 1. I don't think we will make it either. June 15th maybe. Sincerely, Joshua D. Drake ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] [GENERAL] Request from eWeek for 7.3 comments
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 new features, coupled with the additional features added by Mammoth PostgreSQL such as pre-forked connections, stream level compression and Mammoth LXP (the PostgreSQL Application server), PostgreSQL is set to take center stage from products such as MySQL for delivering enterprise class applications to the database market. Sincerely, Joshua D. Drake Co-Founder Command Prompt, Inc. Co-Author Practical PostgreSQL Bruce Momjian wrote: I just spoke with Lisa Vaas from eWeek. She is writing an article on the upcoming PostgreSQL 7.3 release. (The release of 7.3 is scheduled for tomorrow.) She would like comments from users about the upcoming 7.3 features, listed at: http://developer.postgresql.org/docs/postgres/release.html#RELEASE-7-3 If you are interested, please reply to this email with any comments you might have. I have directed replies to her email address. She would like comments within the next few hours, until midnight EST. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] PostgreSQL v7.3.2 Released -- Permission denied from pretty mucheverywhere
Hello folks, Been trying to test the latest source but the following places give permission dened when trying to download: ftp.postgresql.org ftp.us.postgresql.org ftp2.us.postgresql.org mirror.ac.uk Anybody got one that works? J Oliver Elphick wrote: On Wed, 2003-02-05 at 20:41, Laurette Cisneros wrote: I was trying from the postgresql.org download web page and following the mirror links there...and none of them that I was able to get to (some of them didn't work) showed 7.3.2. I got it from mirror.ac.uk yesterday ---(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] PostgreSQL v7.3.2 Released -- Permission denied from pretty much
Hello, Pardon me while I pull my book out of various dark places. It has been a very long week. I got it. Thanks. Sincerely, Joshua Drake Tom Lane wrote: Joshua D. Drake [EMAIL PROTECTED] writes: Been trying to test the latest source but the following places give permission dened when trying to download: ftp.postgresql.org ftp.us.postgresql.org ftp2.us.postgresql.org mirror.ac.uk I just started a download from ftp.us.postgresql.org, and it seems to be working fine. We've not heard other complaints, either. Sure the problem's not on your end? regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Postres dilemma
Hello, Perhaps you could provide some more detailed information? Example of queries? Type of hardware? Operating system? Why are you running a vacuum every 45 seconds? Increase your fsm_pages and run it every hour. Are you sure the vacuums are trampling eachother and thus getting more than one vacuum running at a time? J Neeraj Sharma wrote: Hi I am using Postgres 7.3.4 over linux Redhat 7.3 on i686 machine. My app has one parent table and five child tables. I mean the parent table has a primary key and child tables have foreign key relationship with parent. My App is doing 500 inserts initially in each table. After all this done, we inserting 50 in each table and deleting previous 50 records every seconds. System performs well for awhile (30 Hrs). After 30 hrs I seen that dir size of $PGDATA/base dir is keep on growing and to goes up to 2G in 48 hrs. App is also doing vacuum every 45 seconds. Every time vacuum is triggered, the system goes extreamly slugginsh, and results in various errors like deadlock detected(confirmed in the $PGDATA/../LOG/logfile). vmstat is also showing that blocks sents to the block device (disk) is going crazy. I do not know what is the remedy for this problem. If someone has come across to the issue, please help me as soon as possible. ++ NOTE: I can not use Postgres 7.4 and higher releases beacuse postmaster crashes gauranteed in (20hrs). I have already reported this bug many times (Bug # 1104 is one of them). All crashes show the same behavior and error messages. (specified item offset is too large) ++ I appreciate if some one have the solution for my problem. otherwise it looks like all our app development done on top of Postgres is going in vain. Thanking you in advance. Neeraj K Sharma email: [EMAIL PROTECTED] [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- 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 4: Don't 'kill -9' the postmaster
[HACKERS] vacuumdb: vacuuming of database testdonors failed: ERROR: invalid memory alloc request size 3221225472
Hello, Using community PostgreSQL 7.4.2 I have tried to vacuum this database to no avail. Everytime I try I get this referenced errror. I even dumped and restored to a new database an get the same error. I was also able to reindex the database but no help there. Not much to say on google... Databaes is about 50 megs of mostly text. Less than 5 megs in large objects. Hardware/OS is: Dual Athlon MP 2800 3 Gig ECC Ram 3Ware Hardware Raid 7 SATA Drives in a RAID 10 (1 hot spare). Fedora Core 1 Any thoughts? Sincerely, Joshua D. Drake -- 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 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Frequently updated tables
Also he said that the problem was solved with enough lazy VACUUM scheduling. I don't understand why he doesn't want to use that solution. Because even lazy VACUUM is horrendous to performance but as I said in a further post this has been pretty much fixed by (Jan I believe) in 7.5. Sincerely, Joshua D. Drake -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Frequently updated tables
Sigh, because vacuums take away from performance. This is a known issue that has been pretty much resolved for 7.5. Vacuum in 7.5 does not take even close to as much IO resources. Imagine a table that has to be updated on the order of a few thousand times a minute. Think about the drop in performance during the vacuum. On a one row table, vacuum is not so bad, but try some benchmarks on a table with a goodly number of rows. ---(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 -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(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] I just got it: PostgreSQL Application Server -- a
The "PostgreSQL Enhanced Server" (How's that name? Maybe we call it Zerver and use PEZ?) idea is how to take the excellent core of PostgreSQL and productize it in much the same way distributions take the Linux kernel and may a GNU/Linux system. It would seem to me that this is more correct in the commercial space. Of course I am biased but what you are talking about sounds a whole lot like RedHat Enterprise versus Fedora etc J Even if I find the concepts as such very interesting, I think the term "Application Server" is very misleading. People would get very confused and place PostgreSQL in the same category as JBoss, Jonas, Apache Geronimo, IBM Websphere, BEA Weblogic to name a few well known App-servers. IMHO, you really need some other umbrella name for this. Kind regards, Thomas Hallgren ""Carl E. McMillin"" [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Jumping on that bandwagon with all 6 feet! Carl |};-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:38 PM To: [EMAIL PROTECTED] Subject: [HACKERS] I just got it: PostgreSQL Application Server -- a new project. I have been harping for the last few days (years, actually) about tweaks and changes to PostgreSQL for a number of reasons ranging from session management to static tables. I even had a notion to come up with msession on PostgreSQL. I have been incorporating full text search, recommendations, and a slew of other features into PostgreSQL, but you know what? While it does touch Postgre in a real sense, it is not strictly SQL. It is about how to create applications with PostgreSQL. That's what we're missing, Coneptually, PostgreSQL is strictly a database and the core team (rightly so) is fundimentally happy with that aspect of it. Maybe we need a pgfoundary project called "PostgreSQL Application Server." Like Apache Tomcat or regular apache or PHP, PostgreSQL could form the SQL base of a far more intricate and flexable framework that encompases a lot of the various features that could provide "application sever" features from PostgreSQL. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED] ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings -- 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] warning missing
Hello, You all are behind... Python is king. Sincerely, Joshua D. Drake Gaetano Mendola wrote: Thomas Hallgren wrote: Greg, You don't like Java/C#. I do. What appear here is that you hate C++. I'm a C++ developer since long time now, and I can not use JAVA and or C# just for a couple of reason: 1) Java was supposed to be platform compatible: in thereality is not really true. 2) I can not use the RAII Idiom, or at least without be a joggler 3) I miss the const modifier for methods, and I really can not be sure of what happen to my objects when are used around. Do you want now speak about the missing template feature? Don't say template are the same of Generics. Regards Gaetano Mendola ---(end of broadcast)--- TIP 8: explain analyze is your friend -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] xeon processors
Hello, I seem to recall that HyperThreading and PostgreSQL != good stuff... There was a whole bunch of stuff recently on this... google the archives. Sincerely, Joshua D. Drake Jaime Casanova wrote: Hi all, Can anyone tell me if postgresql has problems with xeon processors? If so, there is any fix or project of fix it? Thanx in advance, Jaime Casanova *Do You Yahoo!?* http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo. Visíta Yahoo! Noticias http://espanol.yahoo.com/mail_tagline/*http://espanol.news.yahoo.com. -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Win32 version question
So it can't be compiled by other compiler? Say Digital Mars or some Microsoft or Borland compiler? Nope. It needs the GNU tool set. -- 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 4: Don't 'kill -9' the postmaster
Re: [HACKERS] compile errors in new PL/Pler
Christopher Kings-Lynne wrote: gmake[3]: Entering directory `/space/1/home/chriskl/pgsql/src/pl/plperl' gcc -O2 -fno-strict-aliasing -g -fpic -DPIC -I. -I/usr/libdata/perl/5.00503/mach/CORE -I../../../src/include -c -o SPI.o SPI.c -MMD I am going to bet dollars to donuts that it is your perl version. Perl 5.00503 is ancient. Try upgrading to at least 5.6. Sincerely, Joshua D. Drake SPI.xs: In function `XS__spi_exec_query': SPI.xs:51: `aTHX_' undeclared (first use in this function) SPI.xs:51: (Each undeclared identifier is reported only once SPI.xs:51: for each function it appears in.) SPI.xs:51: syntax error before string constant gmake[3]: *** [SPI.o] Error 1 gmake[3]: Leaving directory `/space/1/home/chriskl/pgsql/src/pl/plperl' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/space/1/home/chriskl/pgsql/src/pl' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/space/1/home/chriskl/pgsql/src' gmake: *** [all] Error 2 Chris ---(end of broadcast)--- TIP 8: explain analyze is your friend -- 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 7: don't forget to increase your free space map settings
Re: [HACKERS] compile errors in new PL/Pler
So we have three choices as I see it: 1) revert the change 2) require some minimally recent version of perl 3) fix the issue in place Preferences? Joshua/Andrew -- do you want to take a shot at making this work on perl 5.00503? I personally don't have any desire to make this work on a version of perl that the perl community itself suggests that you should upgrade. Perl 5.00503 is RedHat 6.2 genre... That is scary old. I believe even RedHat 7.3 came with Perl 5.6 and that is old as well. Sincerely, Joshua D. Drake Joe -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] [Plperlng-devel] plperl security
Currently we have this in plperl.c: require Safe; I am thinking of submitting a patch to replace this with use Safe 2.09; to enforce use of a version without the known vulnerability. Any objections? I have none, except will 2.09 work with 5.00503? cheers andrew ___ Plperlng-devel mailing list [EMAIL PROTECTED] http://pgfoundry.org/mailman/listinfo/plperlng-devel -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [Plperlng-devel] Re: [HACKERS] plperl security
Hello, I know there is a patch coming Monday with a great deal of bug fixes. J On Fri, 9 Jul 2004, Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: OK, I have a setup that instead of refusing to load trusted functions if the Safe version is not up to date, forces them to error out by calling elog(ERROR...), thus: andrew=# select tval(); ERROR: trusted perl functions disabled - please upgrade perl Safe module to at least 2.09 This seems like perfectly reasonable recovery to me. Thoughts? Works for me --- and it doesn't leak memory across repeated failures, right? Patch please? regards, tom lane ___ Plperlng-devel mailing list [EMAIL PROTECTED] http://pgfoundry.org/mailman/listinfo/plperlng-devel -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] check point segments leakage ?
Hello, Perhaps you have an open transaction that isn't closing and thus the pg_xlog continues to grow? Sincerely, Joshua D. Drake Gaetano Mendola wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, today I add 4 new columns to a table with 4E+06 rows, I also update to an initial value these new columns. The new columns are 3 INTEGER one of type DOUBLE. The table have also 5 indexes. Immediately after the operation my partition data had an usage increment of 1.2GB. I did a reindex and a vacuum full on that table and 600MB were freed. Now I have an increment of only 600 MB. I use a checkpoint_segments = 16 but in my pg_xlog I have 35 files. Why 35 files ? Where are lost my 600MB ? Also the load increased from 1 to 5 !! Any ideas ? I'm attaching boot graphs ( HD space usage and load ). Regards Gaetano Mendola -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA/Ydh7UpzwH2SGd4RAuhKAKCTftBGjBLSfR+OTy5vHlYpL46TXQCfc65/ VfepMM87dQKvg3rswhGUNL8= =HWHy -END PGP SIGNATURE- ---(end of broadcast)--- TIP 8: explain analyze is your friend -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(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] Anybody have an Oracle PL/SQL reference at hand?
Hello, From I can tell from Oracle pl/SQL programming page 130 ;) it is identical. However Oracle does have thinkgs like EXCEPTION_INIT. Here are the name of the Oracle predefined exceptions: CURSOR_ALREADY_OPEN DUP_VAL_ON_INDEX INVALID_CURSOR INVALID_NUMBER LOGIN_DENIED NO_DATA_FOUND NOT_LOGGED_IN PROGRAM_ERROR STORAGE_ERROR TIMEOUT_ON_RESOURCE TOO_MANY_ROWS TRANSACTION_BACKED_OUT VALUE_ERROR Sincerely, Joshua D. Drake Tom Lane wrote: Can anyone check how well the syntax of plpgsql EXCEPTION, as described at http://developer.postgresql.org/docs/postgres/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING agrees with what Oracle does? I did some googling but couldn't find anything that seemed authoritative. I'm wondering in particular if Oracle allows multiple condition names per WHEN, along the lines of WHEN condition [ , condition ... ] THEN handler_statements Also it would be nice to see a complete list of the condition names that they accept. I whipped up a quick table based on our ERRCODE macro names, see http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/pl/plpgsql/src/plerrcodes.h but I'm certain that's not what we really want to expose to users in the long run. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Version Numbering -- The great debate
Hello, Version 7.5 is as close to a major release as I have seen in the almost 9 years I have been using PostgreSQL. This release brings about a lot of "enterprise" features that have been holding back PostgreSQL in a big way for for a long time. All of my serious customers; potential, existing and past has all at one point or another requested most if not all of the features being released onto the world with 7.5. In fact the only ones that I can think of off the top of my head that isn't in the current list of availables is table partitioning and to a lesser extent two phase commit. This release definately deserves a major version jump. If it were up to me it would be more than one (I would call it 10h for obvious reasons. O.k. the h is a joke but I am serious about the 10) just from a marketing standpoint. I could argue a major version jump just from the fact that we finally have a port to the most used operating system (regardless if that is good or bad) in the world. Sincerely, Joshua D. Drake Tom Lane wrote: Josh Berkus [EMAIL PROTECTED] writes: Even if Savepoints don't make it, we'll still have: Savepoints are in, as is exception-trapping in functions (at least plpgsql, the other PLs are on their own :-(). Some other major improvements you didn't mention: Cross-datatype comparisons are indexable (at least for common combinations); this solves a huge performance gotcha Dependency-aware pg_dump Much more complete support for rowtype operations This is more features worth mentioning than we've ever had in a single release before -- and if you consider several add-ons which have been implemented/improved at the same time (Slony, PL/Java, etc.) it's even more momentous. If this isn't 8.0, then what will be? I tend to agree, and was about to bring up the point myself. regards, tom lane ---(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
Re: [HACKERS] pg_dump bug fixing
This is a non-trivial accident to have happen on a shared machine; once users are dumped, all of their ownerships and permissions go with them. If you have a complex permissions system, better hope you backed up first! I find this behavior highly undesirable, and consider it a bug.The globals dump should just add users, and not delete any. Unless the --clean option is passed, yes I agree with you. The other issue is that it is silly to have to use pg_dumpall to get the globals. A person should be able to pull a pg_dump on a particular database and get everything that is required to run that database. Including users. Joshua D. Drake -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] pg_dump bug fixing
Christopher Kings-Lynne wrote: I've been looking at this for a while now, and will probably give it a go for 7.6/8. Let me know when you do, I'd be interested in collaborating. Command Prompt, if would help could help sponsor this project. Sincerely, Joshua D. Drake Chris -- 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 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] PostgreSQL as an application server
The major disadvantage is that the development environment and tools for in-database languages aren't nearly as rich as your typical standalone environment, which makes programming a pain in the ass for many types of codes. I might have missed something in the intervening years, but I Although the gap still exists within the environment itself, one significant advantage with PostgreSQL is you can use a more native (to the programmer anyway) language to generate your logic. With PostgreSQL alone you can use plPerl, plPython and plPHP. The language itself hasn't change in it's implementation of the pL. You just have to remember to make all ' a '' :) (at least for the most part). Sincerely, Joshua D. Drake don't think anyone has really bridged that gap. The database guys generally don't like running application code in their database, mostly because it creates new failure modes and problems that they have to manage. For example, at least in older versions of Oracle, if you accidentally programmed an infinite loop or some other busy non-functioning state, it took the DBA to kill it. In the course of application development, this could happen many, many times as code was being debugged, much to the annoyance of the DBAs. That said, I don't see any obvious reason why it couldn't be done well with a moderate amount of effort. j. andrew rogers ---(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 -- 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 Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL begin:vcard fn:Joshua D. Drake n:Drake;Joshua D. org:Command Prompt, Inc. adr:;;PO Box 215;Cascade Locks;Oregon;97014;USA email;internet:[EMAIL PROTECTED] title:Consultant tel;work:503-667-4564 tel;fax:503-210-0034 note:Command Prompt, Inc. is the largest and oldest US based commercial PostgreSQL support provider. We provide the only commercially viable integrated PostgreSQL replication solution, but also custom programming, and support. We authored the book Practical PostgreSQL, the procedural language plPHP, and adding trigger capability to plPerl. x-mozilla-html:FALSE url:http://www.commandprompt.com/ version:2.1 end:vcard ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
