Re: [HACKERS] Win32 Question about the right level for the account that PostgreSQL is installed under...
> Sorry to be such a pest. Since an administrator will get this error: > > creating template1 database in u:/msys/1.0/local/pgsql/data/base/1 ... > execution of PostgreSQL by a user with administrative > permissions is not permitted. > The server must be started under an unprivileged user ID to > prevent possible system security compromise. See the > documentation for more information on how to properly start > the server. > child process was terminated by signal 1 > initdb.exe: failed > > What is the highest safe level to do the installation under Win32? Must *not* be a member of the Administrators local group or any group which nests into this group (this includes, of course, Domain Admins, but may include other groups depending on your setup). Must *not* be a member of the Power Users local group or any group which nests into this group. That's all we check. Don't grant it unnecessary privileges either, but that's generally not done by default in most setups. It needs log in as a service outside the normal ones, but no others. If you run as service. Otherwise, just log on locally for you to runas to it. Yes, this needs to go intot he documentation :-( //Magnus ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[HACKERS] Thesis on PostgreSQL
Part of my final year thesis involves creating a database using PostgreSQL. As a way of documentation, is it correct to say that PosgreSQL belongs to the fifth generation of database management systems? Where does MySQL fall into? The fourth generation? Thanks, Newton Eyinagho ___ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] Thesis on PostgreSQL
Am Donnerstag, 2. September 2004 13:00 schrieb Eyinagho Newton: > Part of my final year thesis involves creating a > database using PostgreSQL. As a way of documentation, > is it correct to say that PosgreSQL belongs to the > fifth generation of database management systems? Where > does MySQL fall into? The fourth generation? I'm not aware of any generally accepted definitions of generations of database management systems. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[HACKERS] Last version of configure was built with wrong autoconf release
By chance I noticed that when you tagged 8.0beta2, you rebuilt configure with autoconf 2.59. This is not good when the rest of us are using 2.53. We have to stick to a common standard. We could talk about asking all committers to update to 2.59, but mid-beta is probably not the right time for a tools changeover. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Last version of configure was built with wrong autoconf release
I have both installed, but neither is 'autoconf', so I took the newer one ;( Will keep this in mind on next beta ... sorry about that ... On Thu, 2 Sep 2004, Tom Lane wrote: By chance I noticed that when you tagged 8.0beta2, you rebuilt configure with autoconf 2.59. This is not good when the rest of us are using 2.53. We have to stick to a common standard. We could talk about asking all committers to update to 2.59, but mid-beta is probably not the right time for a tools changeover. regards, tom lane Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] beta2 rpms
On Thursday 02 September 2004 00:20, Joe Conway wrote: > I just posted a source rpm for beta2, along with binary rpms for > fc1-i386, fc2-i386, and fc2-x86_64. > http://www.joeconway.com/postgresql-8.0.0beta/ > BTW, I've been naming these similar to the "official" rpms (e.g. > Postgresql-8.0.0*PGDG.*.rpm) mainly just to be consistent. No one has > complained about it, so I take it that's OK? Sorry, I've been kindof swamped around here. Please name them using, say, a 'JC' instead of 'PGDG' if you don't mind. I appreciate you providing these; however, I do intend to be releasing RPM's soon, but probably not beta2 ones. I have some features I want to work on first, and just simply have not yet had the time to do it. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] version upgrade
On 9/1/2004 9:02 PM, Gaetano Mendola wrote: Jan Wieck wrote: Which is another point I was about to ask. How do these people, running those huge and horribly important databases, ever test a single application change? Or any schema changes for that matter. Do they really type "psql -c 'alter table ...' proddb" and believe they are professional users because they know what they are doing? I do alter table, but of course before to do it, I run my regression test on a database with almost no data inside. Each stored procedure is tested in order to execute each execution path. In 3 years working in this way I had no a singol failure after an alter schema operation. If it is possible to define a representative but smaller dataset for test purposes, that is certainly doable. Some systems are just too complex to do this. SAP for example recommends a 4 stage deployment scenario in case you do your own application development in R/3 systems. You would have one or more development systems, that deliver their changes into test systems with small and not necessarily representative data. If all tests there succeed, the software is transported into the integration test system, which is basically a copy of the production system with full data. Only if that transport and the following tests succeed, you transport exactly the same set of programs and catalog changes into the production system. Otherwise you reset the integration test system back to be a copy of the production system. There are a lot of possible levels between playing russian roulette with your data and being paranoid. If a corrupted database can cause the company to go under, some prefer paranoid. Jan -- #==# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #== [EMAIL PROTECTED] # ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] beta2 rpms
On Thu, 2 Sep 2004, Lamar Owen wrote: > Sorry, I've been kindof swamped around here. Please name them using, say, a > 'JC' instead of 'PGDG' if you don't mind. I appreciate you providing these; > however, I do intend to be releasing RPM's soon, but probably not beta2 ones. > I have some features I want to work on first, and just simply have not yet > had the time to do it. Lamar, I've been meaning to ask for a long time: Why does /var/log/pgsql get installed with the execute bit set? I don't have any other log files with the execute bit on, and can't imagine why that would be necessary or useful. Am I missing something? Also, is there a reason that the init script defaults to redirecting stdout and stderr to /dev/null instead of to /var/log/pgsql? If the DBA doesn't turn on logging in postgresql.conf, then very little output goes to /var/log/pgsql, usually of an important nature like "stopped" or "started" at a certain date. I normally change that first thing after a new install. Just wondering. Thanks, Jon -- Jon Jensen End Point Corporation http://www.endpoint.com/ Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ... ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] version upgrade
Jan Wieck wrote: > On 9/1/2004 9:02 PM, Gaetano Mendola wrote: > >> Jan Wieck wrote: >> >> >>> Which is another point I was about to ask. How do these people, >>> running those huge and horribly important databases, ever test a >>> single application change? Or any schema changes for that matter. Do >>> they really type "psql -c 'alter table ...' proddb" and believe they >>> are professional users because they know what they are doing? >> >> >> I do alter table, but of course before to do it, I run my regression test >> on a database with almost no data inside. Each stored procedure is tested >> in order to execute each execution path. >> In 3 years working in this way I had no a singol failure after an alter >> schema operation. > > > If it is possible to define a representative but smaller dataset for > test purposes, that is certainly doable. Some systems are just too > complex to do this. SAP for example recommends a 4 stage deployment > scenario in case you do your own application development in R/3 systems. > You would have one or more development systems, that deliver their > changes into test systems with small and not necessarily representative > data. If all tests there succeed, the software is transported into the > integration test system, which is basically a copy of the production > system with full data. Only if that transport and the following tests > succeed, you transport exactly the same set of programs and catalog > changes into the production system. Otherwise you reset the integration > test system back to be a copy of the production system. > > There are a lot of possible levels between playing russian roulette with > your data and being paranoid. If a corrupted database can cause the > company to go under, some prefer paranoid. Paranoid means also don't trust in new hw without have test it for a while. How ever if I leave unchanged all interfaces and all my test cases are continuously passing ( 3200 different test in my case ) all the night long I'm quite sure that the schema change will not hurt nothing. However I have to say that add come column, with default value and a check on it is no to doable with very bigtables. Fortunately with the 8.0 you can do these tasks in one shot. Regards Gaetano Mendola ---(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] beta2 rpms
On Thursday 02 September 2004 16:27, Jon Jensen wrote: > I've been meaning to ask for a long time: Why does /var/log/pgsql get > installed with the execute bit set? I don't have any other log files with > the execute bit on, and can't imagine why that would be necessary or > useful. Am I missing something? H I've set the wrong permission mask in the %files list, apparently. > Also, is there a reason that the init script defaults to redirecting > stdout and stderr to /dev/null instead of to /var/log/pgsql? The intent was t use syslog. The new log rotation scheme will likely be tapped this time around, though. > If the DBA > doesn't turn on logging in postgresql.conf, then very little output goes > to /var/log/pgsql, usually of an important nature like "stopped" or > "started" at a certain date. I normally change that first thing after a > new install. Normally the first thing I do is enable and set up syslog support. This way I can use my established syslog infrastructure, where really important log messages not only get logged to disk but get PRINTED. Logs that print are difficult for intruders to mess with, and once one has an established syslog server it's trivial to send all logs from all servers to the one central logging server. I have done this a long time. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Implementation of MMDBMS
Open Source Projects: http://www.garret.ru/~knizhnik/fastdb.html http://sourceforge.net/projects/monetdb Papers: http://citeseer.ist.psu.edu/cha95objectoriented.html http://www.cs.ou.edu/~database/main_memory.htm HTH > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ameya S. Sakhalkar > Sent: Wednesday, September 01, 2004 6:38 PM > To: [EMAIL PROTECTED] > Subject: [HACKERS] Implementation of MMDBMS > > > hi, > > I m a M.Tech student of IIT Bombay. I am working on Implementation of > Main Memory DBMS. Plz let me know, if any1 of u is working on > similar kind > of project. > > Regards, > Ameya. > > - > | Ameya S Sakhalkar,| > | M.Tech(II), CSE, | > | C-720, H12, IIT Bombay. | > | email: [EMAIL PROTECTED] | > | Phone: 9892252239 | > | Visit me at: | > | http://www.cse.iitb.ac.in/~ameya | > > > ---(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] beta2 rpms
Lamar Owen wrote: On Thursday 02 September 2004 00:20, Joe Conway wrote: BTW, I've been naming these similar to the "official" rpms (e.g. Postgresql-8.0.0*PGDG.*.rpm) mainly just to be consistent. No one has complained about it, so I take it that's OK? Sorry, I've been kindof swamped around here. Please name them using, say, a 'JC' instead of 'PGDG' if you don't mind. I appreciate you providing these; however, I do intend to be releasing RPM's soon, but probably not beta2 ones. I have some features I want to work on first, and just simply have not yet had the time to do it. Do you want me to rename them right away, or rename as of beta3? Actually, if you release beta3 rpms I won't bother, so I guess we should coordinate. Thanks, Joe ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
