Re: [pgsql-www] [GENERAL] FTP mirror problems
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Robert Treat > Sent: 09 November 2004 21:14 > To: Marc G. Fournier > Cc: Greg Sabino Mullane; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: [pgsql-www] [GENERAL] FTP mirror problems > > > IMHO they should be left as is. I've certainly had to make > use of older versions of the software in the past, and would > not presume to know when others won't want them in the > future. We keep a link to "latest" in the main directory, > and I'm willing to believe most people are capable of > figuring out which is the latest 7.3.x branch on their own > (at least until I see evidence to the contrary). I was going to write something similar, but seeing as you got there first, 'I agree!' Regard,s dave ---(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: [GENERAL] These Lists Are Being Cut To FOUR
> Hello. My name is Mike Cox. I am in charge of the changing of these > postgresql lists. ... (That was a mock diatribe, correct?) Mike, you are not in charge, you are just leading the point on the RFD since Marc has other priorities. (And believe me, he does.) Take a break from the process for a day. There's no rush. And it really isn't all on your back. If you insist on keeping it that way, the vote will fail, and we'll be back where we were. Are you needing a co-proponent? -- Joel <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] These Lists Are Being Cut To FOUR
On Nov 10, 2004, at 6:23 PM, Joel wrote: Hello. My name is Mike Cox. I am in charge of the changing of these postgresql lists. ... (That was a mock diatribe, correct?) Joel, I believe these posts are spoofs. Mike has not posted anything along these lines before, and the headers are different from his usual posts. Unless he 'fesses up and claims these posts as his own, I'm more than willing to give him the benefit of the doubt. These mailing list/new group threads have been tense enough as it is. :) Regards, Michael Glaesemann grzm myrealbox com ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] These Lists Are Being Cut To FOUR
I'm pretty sure the real poster was not Mike. It's very easy to forge the mail headers, including the From, and comparing this mail with other posts from Mike it's pretty obvious they were written from different places. Cheers, Csaba. On Wed, 2004-11-10 at 10:23, Joel wrote: > > Hello. My name is Mike Cox. I am in charge of the changing of these > > postgresql lists. ... > > (That was a mock diatribe, correct?) > > Mike, you are not in charge, you are just leading the point on the RFD > since Marc has other priorities. (And believe me, he does.) > > Take a break from the process for a day. There's no rush. And it really > isn't all on your back. If you insist on keeping it that way, the vote > will fail, and we'll be back where we were. > > Are you needing a co-proponent? ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] These Lists Are Being Cut To FOUR
> ... > I believe these posts are spoofs. Mike has not posted anything along > these lines before, and the headers are different from his usual posts. Hmm. >>> X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char DD hex) in message >>> header 'X-Mailer' X-Mailer: B\335ANet.org\n ^ Yeah, I think I'm going to agree with you on that. The tone is definitely a little over the top compared to what he's posted before. I should have checked the headers. > Unless he 'fesses up and claims these posts as his own, I'm more than > willing to give him the benefit of the doubt. These mailing list/new > group threads have been tense enough as it is. :) Even if he were to claim it, I'd still give him the benefit of the doubt. Polarhound seems to be enjoying a little pyromania in news.groups. But we probably do need someone from the mail list to go co-proponent with Mike. Unless, of course, the majority of the list would prefer to keep the status quo. -- Joel <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] Lost databases
Hi ! I'm in the ultimate state of dispair. Over the night some of my databases just disapeared. But they did not dissaper totally. I can still connect to them but I cannot dump them. When doing a "select * from pg_database" I see only 2 databases I hardly ever use (they are used once in a couple of mounths). Template0 and template1 are missing. All the databases that I currently use dissapeared! Please help me to restore the integrity of the system. I'm in dense fog here :( Liviu ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] Trying to get postgres to use an index
Firstly, check that all your columns are actually of the same type and
the indexes are where you say they are. Using \d will show this.
Secondly, if you do the EXPLAIN ANALYZE with "set enable_seqscan=off",
what is the output?
Hope this helps,
On Tue, Nov 09, 2004 at 05:02:01PM -0800, Mike Wertheim wrote:
> I have some more info on my indexing situation, and a new question.
>
> In my previous email, I told about 2 tables: Notification and Item,
> which join on a field called ItemID. The joining query didn't execute
> as quickly as I thought it should. I now notice that I have another
> table, Folder, which joins with Item in a similar way, and the
> performance of that join is excellent.
>
> So my new questions is... What makes the Folder join faster than the
> Notification join?
>
>
> Here is some info on the tables, queries, and "explain analyze"
> output...
>
> Item's primary key is ItemID (int4).
> Folder's primary key is ItemID (int4). Folder also contains 4 varchar
> columns, 2 text columns, 6 bool columns, 7 datetime columns and 1 int4
> column.
> Notification has an index on its ItemID (int4) field. Notification also
> contains 7 text columns (1 of them being the primary key), 3 timestamp
> columns and 4 int4 columns.
>
> Folder and Notification have a similar number of rows. "select count(*)
> from folder" returns 193043. "select count(*) from notification"
> returns 223689.
>
>
> The first query is: "select count(*) from FOLDER f, ITEM i where
> f.itemID = i.itemID and i.projectid=7720". This query returns the
> result "5" and executes in less than 1 second.
>
> The second query is: "select count(*) from NOTIFICATION n, ITEM i where
> n.itemID = i.itemID and i.projectid=7720". This query returns the
> result "2" and executes in about 40 seconds.
>
>
> Here's the "explain analyze" output...
>
> The Folder query uses the indexes:
> explain analyze select count(*) from FOLDER f, ITEM i where f.itemID =
> i.itemID and i.projectid=7720; Aggregate (cost=6371.88..6371.88
> rows=1 width=0) (actual time=83.557..83.558 rows=1 loops=1)
>-> Nested Loop (cost=0.00..6371.31 rows=227 width=0) (actual
> time=17.929..83.502 rows=5 loops=1)
> -> Index Scan using item_ix_item_4_idx on item i
> (cost=0.00..2105.51 rows=869 width=4) (actual time=0.098..19.409 rows=51
> loops=1)
>Index Cond: (projectid = 7720)
> -> Index Scan using folder_pkey on folder f (cost=0.00..4.90
> rows=1 width=4) (actual time=1.255..1.255 rows=0 loops=51)
>Index Cond: (f.itemid = "outer".itemid)
> Total runtime: 92.185 ms
>
>
> The Notification query does a sequential scan on Notification:
> explain analyze select count(*) from NOTIFICATION n, ITEM i where
> n.itemID = i.itemID and i.projectid=7720;
> Aggregate (cost=38732.31..38732.31 rows=1 width=0) (actual
> time=40380.497..40380.498 rows=1 loops=1)
>-> Hash Join (cost=2107.69..38731.65 rows=263 width=0) (actual
> time=36341.174..40380.447 rows=2 loops=1)
> Hash Cond: ("outer".itemid = "inner".itemid)
> -> Seq Scan on notification n (cost=0.00..35502.89
> rows=223689 width=4) (actual time=8289.236..40255.341 rows=223689
> loops=1)
> -> Hash (cost=2105.51..2105.51 rows=869 width=4) (actual
> time=0.177..0.177 rows=0 loops=1)
>-> Index Scan using item_ix_item_4_idx on item i
> (cost=0.00..2105.51 rows=869 width=4) (actual time=0.025..0.127 rows=51
> loops=1)
> Index Cond: (projectid = 7720)
> Total runtime: 40380.657 ms
>
>
> So my question is... What difference do you see between the Folder and
> Notification tables that would account for such a big difference in
> query performance? And how can I make the Notification query run about
> as fast as the Folder query?
>
>
>
> ---(end of broadcast)---
> TIP 8: explain analyze is your friend
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
pgplIzIqM9aDi.pgp
Description: PGP signature
Re: [GENERAL] the column in Update
Probably because the bit after the SET is a "column-name" not a reference to a column. There's no point qualifying it in any way since the tablename is given as part of the UPDATE statement. On Tue, Nov 09, 2004 at 06:33:55PM -0800, John Fabiani wrote: > From the 7.4 docs: > A column can be referenced in the form > > correlation.columnname > > correlation is the name of a table (possibly qualified with a schema name), > or > an alias for a table defined by means of a FROM clause, or one of the key > words NEW or OLD. (NEW and OLD can only appear in rewrite rules, while other > correlation names can be used in any SQL statement.) The correlation name and > separating dot may be omitted if the column name is unique across all the > tables being used in the current query. (See also Chapter 7.) > > So then why does this not work: > Update tablename set tablename.columnName = 'somedata' where . > > John > > ---(end of broadcast)--- > TIP 8: explain analyze is your friend -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. pgpH7XpDsJLAg.pgp Description: PGP signature
[GENERAL] updateString error in PostgreSQL7.4 with JDBC
Hi,
I have a problem with PostgreSQL 7.4. (With the old one 7.3 no probllem.)
I create a connection and a statement :
Class.forName("org.postgresql.Driver");
conn = DriverManager.getConnection(
O_Constants.DB_CONNECTION_URL,
O_Constants.DB_CONNECTION_USERNAME,
O_Constants.DB_CONNECTION_PASSWORD);
st = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
rs = st.executeQuery("select * ...";
Then:
rs.updateString(20 , ...);
The error is:
org.postgresql.util.PSQLException: Cannot update the result set because
it is either before the start or after the end of the results.
at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.updateValue(AbstractJdbc2ResultSet.java:1595)
at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.updateString(AbstractJdbc2ResultSet.java:1193)
at admin.ValidationRequest.doGet(ValidationRequest.java:43)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:324)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:395)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:536)
The JDBC is:
pg74.215.jdbc3.jar
If you have any comments, please help.
Thanks...
---(end of broadcast)---
TIP 8: explain analyze is your friend
Re: [GENERAL] Lost databases
Let's start with the version of postgresql you're using. Next, were you running VACUUM FULL regularly? It sounds like XID wraparound to me, no idea how to solve that. Got backups? On Wed, Nov 10, 2004 at 12:56:33PM +0200, Liviu BURCUSEL wrote: > Hi ! > > I'm in the ultimate state of dispair. Over the night some of my > databases just disapeared. But they did not dissaper totally. I can > still connect to them but I cannot dump them. When doing a "select * > from pg_database" I see only 2 databases I hardly ever use (they are > used once in a couple of mounths). Template0 and template1 are missing. > All the databases that I currently use dissapeared! > > Please help me to restore the integrity of the system. I'm in dense fog > here :( > > Liviu > > ---(end of broadcast)--- > TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. pgp1HWUoEE3X7.pgp Description: PGP signature
Re: [GENERAL] These Lists Are Being Cut To FOUR
Richard Huxton wrote > Joel wrote: > > > > But we probably do need someone from the mail list to go co-proponent > > with Mike. > > > > Unless, of course, the majority of the list would prefer to keep the > > status quo. > > I must admit I'm not clear what difference this makes to those of us > subscribed to the mailing lists. Is the following correct? > > 1. We already have a news<=>mail gateway > 2. The namespace is not officially recognised which means many news > servers don't provide a feed. > 3. Mike Cox would like to go through the process to get some of these > names in the official hierarchy, thus spreading access > 4. All lists will continue to be available via news.postgresql.org > > If so, it seems that the only difference I (as a mail-based user) will > see is more people posting via newsgroups rather than email. > > Am I missing something here? No, not really. It raises the profile of the project a bit, makes access to PostGreSQL a little easier for people who find usenet easier or cheaper to use than mailing lists. I don't think it's worth distracting the developers over it, but if some of the users have some spare time to push it through, it might be worth the effort. And it would show support for usenet policy. Good neighbor stuff, you know. Karma, as they say. -- Joel <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] updateString error in PostgreSQL7.4 with JDBC
It is ok. I fetch the row with no problem.
The error is only in update types like updateString , updateRow,
updateInt...
ps.You are right JDBC list is appropriate.
Richard Huxton wrote:
Suha Onay wrote:
Hi,
I have a problem with PostgreSQL 7.4. (With the old one 7.3 no
probllem.)
You might get a better response from the jdbc list.
I create a connection and a statement :
Class.forName("org.postgresql.Driver");
conn = DriverManager.getConnection(
O_Constants.DB_CONNECTION_URL,
O_Constants.DB_CONNECTION_USERNAME,
O_Constants.DB_CONNECTION_PASSWORD);
st = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
rs = st.executeQuery("select * ...";
Then:
rs.updateString(20 , ...);
The error is:
org.postgresql.util.PSQLException: Cannot update the result set
because it is either before the start or after the end of the results.
What happens if you fetch a row first?
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] I have had enough
I've had it up to my testicles with this fucking RFD. I can't take it no more. Somebody really needs to take over for me. God damn that cum-swallowing nigger-loving faggot-ass cocksucker Marc for creating such a fucking mess. Let him clean it up, that cocky son of a cunt that his mother was. I quit. Find another sucker to fix this shit. Blow it out your diarrhea-coated unwiped smelly butt-fucked asshole, Marc you fucko. Mike Cox [EMAIL PROTECTED] ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] I have had enough
On Wed, 2004-11-10 at 13:56 +, Mike Cox wrote: > I've had it up to my... I presume this is another forged mail; the headers show that it came through mail3.lidya.net, not yahoo.com. Marc, if we are to be subjected to offensive forgeries like this, do you need to put something in the automatic checking to guard against forged sender addresses? -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA "But thanks be to God, which giveth us the victory through our Lord Jesus Christ." I Corinthians 15:57 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] I have had enough
On Wed, 2004-11-10 at 14:56, Mike Cox wrote (or didn't write): I guess that pretty much firmly identifies this list as an unmoderated list, non? ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[SPOOFED] Nothing to see here (was:Re: [GENERAL] I have had enough)
[all content snipped] Spoofed again. Nothing to see here. -- 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 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[GENERAL] Ping Mike Cox
Hey Mike Cocks!!! Kiss my bullocks you bloody wanker! Go bugger off and take your yank arse to Burger King, you uncultured American cretin. Twits like you make me proud to be a Brit. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA \"But thanks be to God, which giveth us the victory through our Lord Jesus Christ.\" I Corinthians 15:57 ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] I'm about to release the next postgresql RFD.
On Tue, 2004-11-09 at 16:37 -0800, Mike Cox wrote: > The ones not on the list to be made into the big 8 will always be accessible > from the news.postgresql.org server. > > Also, please, if I've missed an important group you think SHOULD be in the > big 8, please let me know in this thread. pgsql-performance gets a lot of posts and is probably relevant to nearly all users. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA "But thanks be to God, which giveth us the victory through our Lord Jesus Christ." I Corinthians 15:57 ---(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: [GENERAL] Ping Mike Cox
* Oliver Elphick ([EMAIL PROTECTED]) wrote: > Twits like you make me proud to be a Brit. Gee, I wonder if it was forged...? <[EMAIL PROTECTED]> Yup. Stephen signature.asc Description: Digital signature
Re: [GENERAL] Ping Mike Cox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is someone under way to tar-and-feather the originator of that nuisance? Mit freundlichem Gruß / With kind regards Holger Klawitter - -- lists klawitter de -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFBki281Xdt0HKSwgYRApPaAJ96qUCY/9pN59ikMY5M9iuke87JogCcChJV kMn4nS2FH/q10e8dMsxa26Q= =b1Z9 -END PGP SIGNATURE- ---(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
[GENERAL] Rolling back an update
Is it possible to undo a transaction after it has completed (using 8 beta1) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] FW: Proper nesting of hierarchical objects
I missed the original post, but I think you both might want to do some googling on nested set. Robert Treat On Tue, 2004-11-09 at 11:40, Garris, Nicole wrote: > We've actually implemented this kind of thing in a different DBMS. The > physical design consists of a single "organization" table that's something > like: > > Org_key (primary key) > Org_type (group, company, etc.) > Org_level (group is 1, company is 2, etc.) > Org_parent_key (foreign key to org that encompasses this org; this is a > "recursive relationship", i.e., a foreign key to the same table) > Org name, address, etc. > > Advantages of this design: > - Its normalized, with the exception of org_level which could be derived by > counting how far down this organization is in the hierarchy > - Re-orgs are pretty easy, even promotions/demotions (level 3 becomes level > 4, etc.) > - If a department moves to a different branch, its simply a matter of > changing the org_parent_key > - Easy to add another level below department (pretty common in my > organization) > > My programmers hate it, but I'm not certain why. It seems easy to me to > create views that hide the recursion. There might be performance issues ... > > Actually, a more flexible design has 2 tables. Table 1 is the org table: > > Org_key (primary key) > Org_type > Org_level > Org name, address, etc. > > Table 2 is the org relationship table (see below). The primary key is > org_key + org_parent_key. > > Org_key > Org_parent_key > Relationship_type > > Relationship type could be R for "responsible to", B for "budgets for", > etc., if organizations can have more than one hierarchy (yes it does happen > in ours). > > Sorry if I didn't completely answer your question. Also, I don't know what > an "adjacency list" is. > > -Original Message- > From: Michael Glaesemann [mailto:[EMAIL PROTECTED] > Sent: Monday, November 08, 2004 2:40 AM > To: '[EMAIL PROTECTED]' General > Subject: [GENERAL] Proper nesting of hierarchical objects > > Hi all. > > I'm working (well, rather, reworking) a database schema that, in part, > models a company organizational structure. For example: > > group > company > division > head office > department > department > branch > department > department > branch > department > department > division > company > division ... > > I would like to model each node of this hierarchy as a generic "org", > as they will all share a lot of characteristics, such as each will have > an address, phone numbers, email addresses (most departments have one > email address rather than an email address for each person... but > that's not my problem :). I'd prefer to model this with nested sets > rather than an adjacency list for easy summaries, but either way, I'd > like to make sure they nest properly, so I don't end up with companies > as children of departments, for example. > > What I've done so far is assign an org_type (e.g., group, company, > division) to each org. My first thought was to assign each org_type a > number, and set the numbers such that parents had numbers higher than > children (or vice versa), and enforce that with triggers. One drawback > was that I might want to use department as a catchall for anything > relatively small, so a department could be a parent of another > department. Enforcing this could be implemented by requiring the parent > org_type number to be greater than or equal to the child org_type > number, but that would also allow, for example, companies to nest in > companies, which is undesirable. > > My second thought was to set up a table that mapped allowable > parent-child relations, and again, enforce immediate parent-child > relationship validity using triggers. This is beginning to feel a bit > hackish to me, so I thought I'd ask if anyone had some advice, words of > encouragement, or pointers to where I might find information on > modeling this. > > Comments, suggestions, ideas, hints, criticism appreciated! > > Regards, > > Michael Glaesemann > grzm myrealbox com > > > ---(end of broadcast)--- > TIP 7: don't forget to increase your free space map settings > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > >http://archives.postgresql.org ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] Analyse - max_locks_per_transaction - why?
Dear PostgreSQL experts,
This is with version 7.4.2.
My database has grown a bit recently, mostly in number of tables but
also their size, and I started to see ANALYSE failing with this message:
WARNING: out of shared memory
ERROR: out of shared memory
HINT: You may need to increase max_locks_per_transaction.
So I increased max_locks_per_transaction from 64 to 200 and, after doing
a /etc/init.d/postgresql/restart rather than a
/etc/init.d/postgresql/reload, it seems to work again.
Naively I imagined that ANALYSE looks at each table in turn,
independently. So why does it need more locks when there are more
tables? Isn't "ANALYSE" with no parameter equivalent to
for i in all_tables_in_database {
ANALYSE i;
}
I'm working in a memory-poor environment (a user-mode-linux virtual
machine) and I'm a bit concerned about the memory overhead if I have to
keep increasing max_locks_per_transaction just to keep ANALYSE happy.
As an aside, what I really need in this particular case is to analyse
all of the tables in a particular schema. Having "ANALYSE schemaname"
or "ANALYSE schemaname.*" would be great. I presume that I can write a
function to get the same effect - has anyone already done that?
Regards,
Phil Endecott.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] These Lists Are Being Cut To FOUR
On Wed, 10 Nov 2004, Michael Glaesemann wrote: On Nov 10, 2004, at 6:23 PM, Joel wrote: Hello. My name is Mike Cox. I am in charge of the changing of these postgresql lists. ... (That was a mock diatribe, correct?) Joel, I believe these posts are spoofs. Mike has not posted anything along these lines before, and the headers are different from his usual posts. Unless he 'fesses up and claims these posts as his own, I'm more than willing to give him the benefit of the doubt. These mailing list/new group threads have been tense enough as it is. :) Agreed from here ... as frustrated as some of Mike's posts have shown him to be, he's never gone "over the edge" that I've seen ... *shrug* 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: [GENERAL] I have had enough
On Wed, 10 Nov 2004, Oliver Elphick wrote: On Wed, 2004-11-10 at 13:56 +, Mike Cox wrote: I've had it up to my... I presume this is another forged mail; the headers show that it came through mail3.lidya.net, not yahoo.com. Marc, if we are to be subjected to offensive forgeries like this, do you need to put something in the automatic checking to guard against forged sender addresses? I'm not sure what can be put in place above/beyond what we already do ... I could put "offensive language" filters in place, maybe >:) 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
Re: [GENERAL] Rolling back an update
mike wrote: > Is it possible to undo a transaction after it has completed (using 8 > beta1) Using the new point-in-time recovery feature, but you need to set that up first. -- 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
Re: [GENERAL] Important Info on comp.databases.postgresql.general
--- "Gary L. Burnore" <[EMAIL PROTECTED]> wrote: > On 9 Nov 2004 15:51:24 -0800, > [EMAIL PROTECTED] wrote: > > >This is a very unfair limitation. > > Stop top posting. > > >If there is a ballot, it should be posted to each > of the individual mailing lists. > > That's not how it works. > > >When/if a ballot appears in News Announce > Newgroups, I will copy/paste and e-mail the > >ballot to each of the PostgreSql mailing lists, > once per week during > >the 3 weeks of voting. The mailing list users will > be most affected by > >any voting outcome. I will not allow them to be > left out of the > >process. Many of the list subscribers do not use > Usenet. I never posted > >to a newsgroup before today. > > > >Additionally, I encourage all list members to vote > yes. Please get > >everyone you know to vote. We need to exceed the no > votes by 100 in > >order to pass. I am affiliated with a network of > over 60 PostgreSql > >users/developers, and I will e-mail each one of > those people a ballot, > >and it is safe to presume that essentially all of > them will vote yes. I > >encourage all proponents of saving the lists to do > exactly the same, > >within their scope of influence. > > You're trying to get it to fail, eh? Nice going. > > > >I am stupefied by the downright arrogance of most > of the news.groups > >readership. > > Please. We're trying to help you fix something > that's broken. ??? As a longstanding reader of the pgsql- mailinglists, (including via news.postgresql.org on occasion), all I see is some outsiders trying to help us "fix" a problem that does not exist. And yes, I have read most of the messages that have passed by in these threads. After all that, I still don't see the benefit. Perhaps that is why these conversations have been carried on almost totally by people who do not post to the pgsql lists. > > > You people have the audacity try and dictate rules > of > >matters that do not affect your lives in the least. > > I've dealt with the day to day workings of USENet > for more than 10 > years and there are a LOT of people who've been > doing it longer. > > Try not making so many assumptions. > > > > >Mr. Pauli Vaurio > > > -- > [EMAIL PROTECTED] dot com > --- > How you look depends on where you > go. > --- > Gary L. Burnore | > ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > | > ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > DataBasix | > ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³ > | ÝÛ³ 3 4 1 4 > 2 ݳ޳ 6 9 0 6 9 ÝÛ³ > Black Helicopter Repair Svcs Division | Official > Proof of Purchase > === > Want one? GET one! > http://signup.databasix.com > === > > ---(end of > broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > __ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Lost databases
--- Liviu BURCUSEL <[EMAIL PROTECTED]> wrote: > Hi ! > > I'm in the ultimate state of dispair. Over the night > some of my > databases just disapeared. But they did not dissaper > totally. I can > still connect to them but I cannot dump them. When > doing a "select * > from pg_database" I see only 2 databases I hardly > ever use (they are > used once in a couple of mounths). Template0 and > template1 are missing. > All the databases that I currently use dissapeared! > > Please help me to restore the integrity of the > system. I'm in dense fog > here :( What Postgresql version is this? Your problem sounds like "oid wraparound". There was a recent discussion of this on the list; try the list archives to see what was recommended in that case. > > Liviu > > ---(end of > broadcast)--- > TIP 5: Have you checked our extensive FAQ? > > > http://www.postgresql.org/docs/faqs/FAQ.html > __ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] Important Info on comp.databases.postgresql.general
Jeff Eckermann wrote: > ??? As a longstanding reader of the pgsql- > mailinglists, (including via news.postgresql.org on > occasion), all I see is some outsiders trying to help > us "fix" a problem that does not exist. And yes, I > have read most of the messages that have passed by in > these threads. After all that, I still don't see the > benefit. Perhaps in parallel with the Usenet community voting whether they want to receive posts from the mailing lists, we can have the mailing list subscribers vote on whether they want to receive messages from the Usenet or want to have their messages forwarded to the Usenet. That might be interesting. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[GENERAL] Error connecting using pgadmin from different computer !!
Hello, I get an error in my log when connecting to postgres server on Windows. Postgres version : 8.0.0-beta4 LOG TEXT 2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, token "192.168.2.1/254" 2004-11-10 11:22:47 FATAL: missing or erroneous pg_hba.conf file 2004-11-10 11:22:47 HINT: See server log for details. Configuration file pg_hba.conf hostall all 192.168.2.1/254md5 hostall all 127.0.0.1/32 md5 Any ideas how to fix it ?? Thanks ! Goutam Confidentiality Notice The information contained in this e-mail is confidential and intended for use only by the person(s) or organization listed in the address. If you have received this communication in error, please contact the sender at O'Neil & Associates, Inc., immediately. Any copying, dissemination, or distribution of this communication, other than by the intended recipient, is strictly prohibited. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[GENERAL] Modifying FK constraints
Title: Message Greetings. Is it possible to modify a foreign key constraint and force it to cascade on update? If there is no such SQL command, then is it possible to update some system tables to accomplish this? The problem is that I have a bunch of tables with FK constraints and I need to update primary key values in a lot of these tables. FK constraints were declared, but without cascading updates. Now, I am trying to modify all of them to cascade updates so that I can change primary keys and have these changes propaged to the referencing values. What would be the easiest solution for this? Thanks. Oleg
Re: [GENERAL] Modifying FK constraints
Oleg Lebedev wrote: Greetings. Is it possible to modify a foreign key constraint and force it to cascade on update? If there is no such SQL command, then is it possible to update some system tables to accomplish this? BEGIN; ALTER TABLE t1 DROP CONSTRAINT ... ALTER TABLE t1 ADD CONSTRAINT ... COMMIT; Note that this will trigger a re-examination of all the values to check the constraint is valid. Also you may have to quote constraint names. If they are generated as $1 you will need to refer to them as "$1". Full details in the "SQL Commands" chapter under "ALTER TABLE" -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Important Info on comp.databases.postgresql.general
> Perhaps in parallel with the Usenet community voting whether they want > to receive posts from the mailing lists, we can have the mailing list > subscribers vote on whether they want to receive messages from the > Usenet or want to have their messages forwarded to the Usenet. That > might be interesting. If it isn't already in mailman, it would be an interesting option to add to mailman's web interface to give subscribers the option to include or exclude posts being gatewayed from USENET. (I could use that feature on some lists I run.) -- Mike Nolan ---(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: [GENERAL] Modifying FK constraints
On Wed, Nov 10, 2004 at 10:00:02AM -0700, Oleg Lebedev wrote: > Is it possible to modify a foreign key constraint and force it to > cascade on update? If there is no such SQL command, then is it possible > to update some system tables to accomplish this? You can drop and add constraints with ALTER TABLE. -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Modifying FK constraints
Thanks, but the problem here is that I have multiple replicated databases with the same schema and each of them contains numerous tables. So, dropping and re-creating FK constraints manualy is not feasible, and I am trying to automate this process. Each table contains a primary key column "objectid", so this should make it simpler to apply the same procedure to all tables. So, what I want to do is: FOR EACH TABLE 1. Find out if there is an FK referencing its "objectid" column 2. If there is one, then either drop and recreate the FK or modify FKs system property to force cascading of updates. I would rather prefer updating the system table. So, I would need to know answers to the following questions: 1. How can I find out what FKs reference a the given column based on the system table information? 2. What system table do I need to update to force an FK constraint to cascade updates? Thanks. Oleg -Original Message- From: Richard Huxton [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 10, 2004 10:23 AM To: Oleg Lebedev Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] Modifying FK constraints Oleg Lebedev wrote: > Greetings. > > Is it possible to modify a foreign key constraint and force it to > cascade on update? If there is no such SQL command, then is it > possible to update some system tables to accomplish this? BEGIN; ALTER TABLE t1 DROP CONSTRAINT ... ALTER TABLE t1 ADD CONSTRAINT ... COMMIT; Note that this will trigger a re-examination of all the values to check the constraint is valid. Also you may have to quote constraint names. If they are generated as $1 you will need to refer to them as "$1". Full details in the "SQL Commands" chapter under "ALTER TABLE" -- Richard Huxton Archonet Ltd ---(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: [GENERAL] Modifying FK constraints
On Wed, 10 Nov 2004, Oleg Lebedev wrote: > Is it possible to modify a foreign key constraint and force it to > cascade on update? If there is no such SQL command, then is it possible > to update some system tables to accomplish this? > > The problem is that I have a bunch of tables with FK constraints and I > need to update primary key values in a lot of these tables. FK > constraints were declared, but without cascading updates. Now, I am > trying to modify all of them to cascade updates so that I can change > primary keys and have these changes propaged to the referencing values. > > What would be the easiest solution for this? The easiest solution is to drop the constraint and re-add it with the changed parameters. This will however check the constraint against the current table data. It would probably be possible to change the behavior by updating the appropriate rows in the system tables. You would need at least to change tgfoid in pg_trigger for the after update trigger on the referenced table. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Analyse - max_locks_per_transaction - why?
Phil Endecott <[EMAIL PROTECTED]> writes: > Naively I imagined that ANALYSE looks at each table in turn, > independently. So why does it need more locks when there are more > tables? 7.4 runs a database-wide ANALYZE as a single transaction, so the locks accumulate. This was recognized to be a bad idea :-(. 8.0 is a bit smarter. The best bet in 7.4 is probably to use VACUUM ANALYZE rather than analyzing separately. That will force it to use a transaction per table. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Error connecting using pgadmin from different computer
My understanding was it means ip range of 1 to 254. 192.168.2.1 to 192.168.1.254 > -Original Message- > From: Wilson, David [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 10, 2004 12:05 PM > To: Goutam Paruchuri > Subject: RE: [GENERAL] Error connecting using pgadmin from > different computer !! > > > Maybe the 254 at the end of the ip address? Should be between > 0 and 32 or > 128 according to the text in the pg_hba.conf file. I'm no > expert though :) > > > -Original Message- > From: Goutam Paruchuri [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 10, 2004 10:32 AM > To: [EMAIL PROTECTED] > Subject: [GENERAL] Error connecting using pgadmin from > different computer !! > Importance: High > > > Hello, > > I get an error in my log when connecting to postgres server > on Windows. > Postgres version : 8.0.0-beta4 > > LOG TEXT > > 2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program > Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, > token "192.168.2.1/254" > 2004-11-10 11:22:47 FATAL: missing or erroneous pg_hba.conf > file 2004-11-10 11:22:47 HINT: See server log for details. > > Configuration file pg_hba.conf > > hostall all 192.168.2.1/254 md5 > hostall all 127.0.0.1/32 md5 > > Any ideas how to fix it ?? > > Thanks ! > Goutam > > > > > Confidentiality Notice > The information contained in this e-mail is confidential and > intended for use only by the person(s) or organization listed > in the address. If you have received this communication in > error, please contact the sender at O'Neil & Associates, > Inc., immediately. Any copying, dissemination, or > distribution of this communication, other than by the > intended recipient, is strictly prohibited. > > > ---(end of > broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > Confidentiality Notice The information contained in this e-mail is confidential and intended for use only by the person(s) or organization listed in the address. If you have received this communication in error, please contact the sender at O'Neil & Associates, Inc., immediately. Any copying, dissemination, or distribution of this communication, other than by the intended recipient, is strictly prohibited. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Important Info on comp.databases.postgresql.general
On Wed, 10 Nov 2004, Mike Nolan wrote: Perhaps in parallel with the Usenet community voting whether they want to receive posts from the mailing lists, we can have the mailing list subscribers vote on whether they want to receive messages from the Usenet or want to have their messages forwarded to the Usenet. That might be interesting. If it isn't already in mailman, it would be an interesting option to add to mailman's web interface to give subscribers the option to include or exclude posts being gatewayed from USENET. gatewaying means that there is an address subscribed to the lists that sends all email's to the news server ... a feature like the above would have to be akin to a "don't send to subscriber X" ... Also note that any such restrictions would end up affecting gmane and google as well ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] Modifying FK constraints
In order to find all FK declared on a table I query tg_trigger view. The query lists all FKs declared on the table as well as all the ones referencing the table. I noticed that FKs that are declared on the table have pgtype equal to 21, and FKs referencing the table have pgtype 9 or 17. The following query lists all the FKs declared table 'objective'. Is this the right way to do this? select t.tgconstrname, src.relname, dest.relname, t.tgtype from pg_trigger t, pg_class src, pg_class dest where t.tgrelid=src.oid and t.tgconstrrelid=dest.oid and t.tgisconstraint = 't' and t.tgtype=21 and src.relname='objective'; Thanks. Oleg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Oleg Lebedev Sent: Wednesday, November 10, 2004 10:37 AM To: Richard Huxton Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] Modifying FK constraints Thanks, but the problem here is that I have multiple replicated databases with the same schema and each of them contains numerous tables. So, dropping and re-creating FK constraints manualy is not feasible, and I am trying to automate this process. Each table contains a primary key column "objectid", so this should make it simpler to apply the same procedure to all tables. So, what I want to do is: FOR EACH TABLE 1. Find out if there is an FK referencing its "objectid" column 2. If there is one, then either drop and recreate the FK or modify FKs system property to force cascading of updates. I would rather prefer updating the system table. So, I would need to know answers to the following questions: 1. How can I find out what FKs reference a the given column based on the system table information? 2. What system table do I need to update to force an FK constraint to cascade updates? Thanks. Oleg -Original Message- From: Richard Huxton [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 10, 2004 10:23 AM To: Oleg Lebedev Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] Modifying FK constraints Oleg Lebedev wrote: > Greetings. > > Is it possible to modify a foreign key constraint and force it to > cascade on update? If there is no such SQL command, then is it > possible to update some system tables to accomplish this? BEGIN; ALTER TABLE t1 DROP CONSTRAINT ... ALTER TABLE t1 ADD CONSTRAINT ... COMMIT; Note that this will trigger a re-examination of all the values to check the constraint is valid. Also you may have to quote constraint names. If they are generated as $1 you will need to refer to them as "$1". Full details in the "SQL Commands" chapter under "ALTER TABLE" -- Richard Huxton Archonet Ltd ---(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 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [GENERAL] Error connecting using pgadmin from different computer
Its works if I specify the ipaddress of each client which is being connecting to the server. Its hard to do it on a DHCP network . Any roundabouts ? - Goutam > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Goutam Paruchuri > Sent: Wednesday, November 10, 2004 1:12 PM > To: Wilson, David > Cc: [EMAIL PROTECTED] > Subject: Re: [GENERAL] Error connecting using pgadmin from > different computer > > > My understanding was it means ip range of 1 to 254. > > 192.168.2.1 to 192.168.1.254 > > > -Original Message- > > From: Wilson, David [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, November 10, 2004 12:05 PM > > To: Goutam Paruchuri > > Subject: RE: [GENERAL] Error connecting using pgadmin from > different > > computer !! > > > > > > Maybe the 254 at the end of the ip address? Should be > between 0 and 32 > > or > > 128 according to the text in the pg_hba.conf file. I'm no expert > > though :) > > > > > > -Original Message- > > From: Goutam Paruchuri [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, November 10, 2004 10:32 AM > > To: [EMAIL PROTECTED] > > Subject: [GENERAL] Error connecting using pgadmin from different > > computer !! > > Importance: High > > > > > > Hello, > > > > I get an error in my log when connecting to postgres server on > > Windows. > > Postgres version : 8.0.0-beta4 > > > > LOG TEXT > > > > 2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program > > Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, token > > "192.168.2.1/254" > > 2004-11-10 11:22:47 FATAL: missing or erroneous pg_hba.conf file > > 2004-11-10 11:22:47 HINT: See server log for details. > > > > Configuration file pg_hba.conf > > > > hostall all 192.168.2.1/254md5 > > hostall all 127.0.0.1/32 md5 > > > > Any ideas how to fix it ?? > > > > Thanks ! > > Goutam > > > > > > > > > > Confidentiality Notice > > The information contained in this e-mail is confidential > and intended > > for use only by the person(s) or organization listed in the > address. > > If you have received this communication in error, please > contact the > > sender at O'Neil & Associates, Inc., immediately. Any copying, > > dissemination, or distribution of this communication, other than by > > the intended recipient, is strictly prohibited. > > > > > > ---(end of > > broadcast)--- > > TIP 4: Don't 'kill -9' the postmaster > > > > > Confidentiality Notice > The information contained in this e-mail is confidential and > intended for use only by the person(s) or organization listed > in the address. If you have received this communication in > error, please contact the sender at O'Neil & Associates, > Inc., immediately. Any copying, dissemination, or > distribution of this communication, other than by the > intended recipient, is strictly prohibited. > > > ---(end of > broadcast)--- > TIP 7: don't forget to increase your free space map settings > Confidentiality Notice The information contained in this e-mail is confidential and intended for use only by the person(s) or organization listed in the address. If you have received this communication in error, please contact the sender at O'Neil & Associates, Inc., immediately. Any copying, dissemination, or distribution of this communication, other than by the intended recipient, is strictly prohibited. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [GENERAL] Error connecting using pgadmin from different computer
"Goutam Paruchuri" <[EMAIL PROTECTED]> writes: > My understanding was it means ip range of 1 to 254. You're mistaken. /n means an n-bit netmask. /254 is nonsense. What you probably want is 192.168.2.0/24, which effectively means "all of 192.168.2.*". regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Important Info on comp.databases.postgresql.general
??? As a longstanding reader of the pgsql- mailinglists, (including via news.postgresql.org on occasion), all I see is some outsiders trying to help us "fix" a problem that does not exist. And yes, I have read most of the messages that have passed by in these threads. After all that, I still don't see the benefit. To me, this sounds pretty elitist and exclusionary. Is there a reason why you would not want more people particpating in the discussions here? I myself never participated here until I figured out I could point a usenet reader to news.postgresql.org to view and reply to the list. No way I was going to get hundreds of messages a day in my inbox. As for why not just keep the same system, there are times when news.postgresl.org runs like a dog. 2 or 3 days out of a month, messages take 5 or more seconds to come up. If I and others could use our local news servers, that's less bandwidth, less load for the postgres servers. And that means someone, somewhere is paying less for their contributions to the PG project. ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] [ADMIN] Where is postgresql??
Look it at: ~/usr/local/pgsql Libs: ~/usr/libs/postgresql Francisco Jose Bernabe Pellicer wrote: Hello everybody, I have a computer with Scientific Linux. From a repository I downloaded the packages rh-postgresql-* with the command apt-get install... The thing is that after installing all the packages, I cannot enable postgresql, because there's no /etc/init.d/postgresql file (even not /etc/init.d/rh-posgtresql file, or anything simmilar). From this page I followed the steps from the 7th one, since the postgres user is automatically created: http://sciense.sourceforge.net/downloads.html I hope you have any idea of what's going on. Cheers, ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Error connecting using pgadmin from different computer !!
On Thu, 11 Nov 2004 03:31 am, Goutam Paruchuri wrote: > Hello, > > I get an error in my log when connecting to postgres server on Windows. > Postgres version : 8.0.0-beta4 > > LOG TEXT > > 2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program > Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, token > "192.168.2.1/254" > 2004-11-10 11:22:47 FATAL: missing or erroneous pg_hba.conf file > 2004-11-10 11:22:47 HINT: See server log for details. > > Configuration file pg_hba.conf > > hostall all 192.168.2.1/254 md5 /254 <- that is not a valid subnet mask. /0 - /32 are valid, did you mean /31? > hostall all 127.0.0.1/32 md5 > > Any ideas how to fix it ?? > > Thanks ! > Goutam > > > > > Confidentiality Notice > The information contained in this e-mail is confidential and intended for use > only by the person(s) or organization listed in the address. If you have > received this communication in error, please contact the sender at O'Neil & > Associates, Inc., immediately. Any copying, dissemination, or distribution of > this communication, other than by the intended recipient, is strictly > prohibited. > > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Problem with 7.4.1 and complicated queries
Cheers, The Problems with the database still show up. We upgraded the database to 7.4.6 >From postgresql.conf: shared_buffers = 1 # min 16, at least max_connections*2, 8KB each sort_mem = 2048 # min 64, size in KB vacuum_mem = 8192 # min 1024, size in KB # - Free Space Map - max_fsm_pages = 5 # min max_fsm_relations*16, 6 bytes each max_fsm_relations = 3000# min 100, ~50 bytes each The sympton is that one report that uses a long querie freezes, the correospondig process uses 98% CPU. If I dump the database und run the querie on the new database, everything works fine. SO I justed made the customer a new database and used the backup for the data. But on the nex day, same thing. The reports would freeze. This only happens with one report, not always with the same querie. But if I run the query over the CLI, it also freezes, so it is not the gui or a network timeout. This query worked for over one year, nobody changed something. VACUUM FULL ; ANALYZE; will not change anything. Any hints? Thank you, Jonathan On Sun, 24 Oct 2004 22:00:09 +0200, Jonathan Weiss <[EMAIL PROTECTED]> wrote: > Hi! > > > > > This sounds like maybe you're FSM settings aren't high enough, or you > > aren't analyzing your tables. > > I doubled the values for max_fsm_pages and max_fsm_relations. > > > Try vacuum full and analyze first, and see if that fixes the problem. > > If so, then you either need to vacuum more often, increase your fsm > > ssettings, (or both) and probably need to schedule regular analyzes. > > I tried vacuum full and analyze, but the problem still remains. The > funny thing is, that working on a fresh dumped version works. > > Greets, > Jonathan > ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [GENERAL] index not always used when selecting on a date field
In article <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] ("Miquel van Smoorenburg" ) writes:
>> techdb2=> explain select * from lines where (removed > CURRENT_DATE
>AND removed < '-01-01');
>
>> With 7.3, this query used the index, while with 7.4 it doesn't.
>
>Perhaps you hadn't ANALYZEd in 7.3? AFAICS 7.3 and 7.4 behave
>essentially alike on this point, given comparable statistics.
>
>One thing I did notice in looking at this is that the preferential
>treatment for range constraints only applies when *both* sides of the
>range are un-estimatable. So you need to write something like
>
>WHERE (removed > CURRENT_DATE AND removed < CURRENT_DATE + 1)
>
>to get it to work nicely. I'll see if I can improve on that for 8.0;
>seems like the way you tried ought to work, too.
Well, my problem has been solved by using an immutable function
that returns CURRENT_DATE (thanks for the support!), but this
suggestion doesn't work for me:
techdb2=> vacuum;
WARNING: skipping "pg_shadow" --- only table or database owner can vacuum it
WARNING: skipping "pg_database" --- only table or database owner can vacuum
itWARNING: skipping "pg_group" --- only table or database owner can vacuum it
VACUUM
techdb2=> explain select * from lines WHERE (removed > CURRENT_DATE AND removed
< CURRENT_DATE + 1);
QUERY PLAN
---
Seq Scan on lines (cost=0.00..292.71 rows=3125 width=179)
Filter: ((removed > ('now'::text)::date) AND (removed < (('now'::text)::date
+ 1)))
(2 rows)
Still a sequential scan. Yes, there is an index and it can be used:
techdb2=> explain select * from lines WHERE removed > today();
QUERY PLAN
-
Index Scan using lines_removed_idx on lines (cost=0.00..4.78 rows=1 width=179)
Index Cond: (removed > '2004-11-11'::date)
(2 rows)
Mike.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] the column in Update
Thanks but in the doc's it uses the term 'columnname'. The real issue is the tablename.columnname is supported in MySQL and I'm trying to support Postgres and MySQL with a single code routine. John On Wednesday 10 November 2004 03:31, Martijn van Oosterhout wrote: > Probably because the bit after the SET is a "column-name" not a > reference to a column. There's no point qualifying it in any way since > the tablename is given as part of the UPDATE statement. > > On Tue, Nov 09, 2004 at 06:33:55PM -0800, John Fabiani wrote: > > From the 7.4 docs: > > A column can be referenced in the form > > > > correlation.columnname > > > > correlation is the name of a table (possibly qualified with a schema > > name), or an alias for a table defined by means of a FROM clause, or one > > of the key words NEW or OLD. (NEW and OLD can only appear in rewrite > > rules, while other correlation names can be used in any SQL statement.) > > The correlation name and separating dot may be omitted if the column name > > is unique across all the tables being used in the current query. (See > > also Chapter 7.) > > > > So then why does this not work: > > Update tablename set tablename.columnName = 'somedata' where . > > > > John > > > > ---(end of broadcast)--- > > TIP 8: explain analyze is your friend ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] the column in Update
John Fabiani wrote: > Thanks but in the doc's it uses the term 'columnname'. The real > issue is the tablename.columnname is supported in MySQL and I'm > trying to support Postgres and MySQL with a single code routine. Surely MySQL would also support writing a column name without a table name? -- 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
Re: [GENERAL] [pgsql-general] Daily digest v1.4794 (21 messages)
Yeah.. I'm with you.. I don't really know what all of this is about - I like the way the Postgres mailing list works as it is Are any of the changes being discussed here going to change the content or how we receive the mailing lists?.. What exactly is the problem they thing exists anyways?.. Does this have anything to do with the folks who are posting forged messages? - Greg >??? As a longstanding reader of the pgsql- >mailinglists, (including via news.postgresql.org on >occasion), all I see is some outsiders trying to help >us "fix" a problem that does not exist. And yes, I >have read most of the messages that have passed by in >these threads. After all that, I still don't see the >benefit. > >Perhaps that is why these conversations have been >carried on almost totally by people who do not post to >the pgsql lists. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [GENERAL] Important Info on comp.databases.postgresql.general
Yeah.. I'm with you.. I don't really know what all of this is about - I like the way the Postgres mailing list works as it is Are any of the changes being discussed here going to change the content or how we receive the mailing lists?.. .. The only change I've noticed is that in all the time of reading this list I've not seen jerks posting forged messages like that Certainly not a positive change, but I'm not sure it can be attributed to what is going on... - Greg >??? As a longstanding reader of the pgsql- >mailinglists, (including via news.postgresql.org on >occasion), all I see is some outsiders trying to help >us "fix" a problem that does not exist. And yes, I >have read most of the messages that have passed by in >these threads. After all that, I still don't see the >benefit. > >Perhaps that is why these conversations have been >carried on almost totally by people who do not post to >the pgsql lists. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] the column in Update
John Fabiani <[EMAIL PROTECTED]> writes: > Thanks but in the doc's it uses the term 'columnname'. The real issue is the > tablename.columnname is supported in MySQL and I'm trying to support Postgres > and MySQL with a single code routine. If you want portable code, I suggest conforming to the SQL-standard syntax. The table name is disallowed there according to the spec. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] Postgresql future changes
I am proposing some new changes for this list. 1) Black spook jiggaboo watermelon-eating niggers may not post 2) Penny-pinching Jewish kikes may only post if they contribute money 3) Slant-eyed Asian chinks and gooks may post as much as they like 4) Hairy dago greaseball Italians may only post recipes 5) Cocksucking cum-swallowing homosexual faggots may not post 6) Twat-licking dildo-strapped lesbian dikes may post 7) Taco-eating wetback cockroach Mexicans may not post 8) German krauts may post only if they are not Jews 9) Muslim Arabic terrorist scum may not mailbomb the list 10) That scumbag Marc needs to announce a new moderator EFFECTIVE IMMEDIATELY!!! ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Postgresql future changes
I've blacklisted this IP ... not sure if that will help or not *shrug* On Wed, 11 Nov 2004, Mike Cox wrote: I am proposing some new changes for this list. 1) Black spook jiggaboo watermelon-eating niggers may not post 2) Penny-pinching Jewish kikes may only post if they contribute money 3) Slant-eyed Asian chinks and gooks may post as much as they like 4) Hairy dago greaseball Italians may only post recipes 5) Cocksucking cum-swallowing homosexual faggots may not post 6) Twat-licking dildo-strapped lesbian dikes may post 7) Taco-eating wetback cockroach Mexicans may not post 8) German krauts may post only if they are not Jews 9) Muslim Arabic terrorist scum may not mailbomb the list 10) That scumbag Marc needs to announce a new moderator EFFECTIVE IMMEDIATELY!!! ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] updateString error in PostgreSQL7.4 with JDBC
On Wed, 10 Nov 2004, Suha Onay wrote:
> st = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
> ResultSet.CONCUR_UPDATABLE);
> rs = st.executeQuery("select * ...";
>
> Then:
> rs.updateString(20 , ...);
>
> The error is:
> org.postgresql.util.PSQLException: Cannot update the result set because
> it is either before the start or after the end of the results.
You must be on a row (or the insert row) to update it, you have not shown
any positioning methods (like next()) being called on the ResultSet so it
is left positioned before the first row. I don't know what the 7.3 driver
was actually doing, but this error is the expected behavior of the driver,
unless of course you are doing something else you haven't shown us.
Kris Jurka
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [GENERAL] Proposal: GRANT cascade to implicit sequences
I looked over this thread and can't see any TODO item. Having GRANT
just propogate from the table to a SERIAL sequence doesn't work because
an INSERT into a table is an UPDATE of the sequence.
Is there a TODO here?
---
Tom Lane wrote:
> Greg Stark <[EMAIL PROTECTED]> writes:
> > I can't think of a good approach for migration of old pg_dumps though, so
> > perhaps this is more trouble than it's worth.
>
> That would probably be the major objection to any redefinition of the
> meanings of the individual sequence permissions. We could possibly
> invent a couple of brand new permission bits though, and stipulate that
> "UPDATE" incorporates them both.
>
> > Implicit sequences on the other hand can be migrated easily by ignoring all
> > explicit grants and just looking at the grants on the table.
>
> It's not really that easy. Before we hack up the permissions system like
> this I'd want to see a complete solution, which this is not, because it
> doesn't work in the context of rules. Consider
>
> CREATE TABLE t (id SERIAL ...);
>
> CREATE VIEW v AS SELECT * FROM t;
>
> CREATE RULE r AS ON INSERT TO v DO INSTEAD INSERT INTO t ...
>
> GRANT INSERT ON v TO joeuser;
>
> joeuser will be able to invoke the insertion rule, but nextval() will
> still fail because it doesn't know about the rule context --- it'll
> see joeuser as the current user, not the owner of the rule.
>
> Eventually I'd like to replace the nextval('foo') notation with a parsed
> construct foo.nextval, which is (a) Oracle compatible, (b) able to
> withstand renamings of the foo sequence, and (c) amenable to having the
> permissions check done during rangetable scanning, which would fix the
> rule problem. There is some discussion of this in the pghackers archives.
>
> regards, tom lane
>
> ---(end of broadcast)---
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Important Info on comp.databases.postgresql.general
Currently the mailing list is also hosted in a newsgroup at new.postgresql.org. The news group is not "Official" so it is not carried by all news servers. There are some users who can not participate in a mailing list comfortably for one reason or another. Some of these individuals would like their local USENET provider to carry the news group. Because postgresql isn't official they will not do this. So there is now a movement to make the list official. The extra traffic I believe is coming from the discussion of the USENET people trying to get this done. Most USENET folk are good manor people just like you find on the lists. There are a lot of politics involved in USENET that are not present in your typical mailing list. This is primarily because mailing lists are hosted by the project/group and involve a single mail server where as USENET is many servers and many topics. As near as I can tell the main person pushing for making the list an official news group has inadvertently, or maybe advertently, offended someone with his politics, and/or lack of knowledge of the USENET process. Nothing big but with politics comes grudges etc. The other thing that I have noticed is people seem to get into more flame wars on USENET compared to mailing lists. There are many reasons for this but they are irrelevant. Part of this process of flaming and what not is the jerk forged message to piss people off. In particular I think the forger was attempting to sway the creditability , of the person being forged, to the people that make the USENET decisions. The chatter is there to inform anyone who might be fooled. If this push is successful are we likely to see a few jerks posting on the list via USENET? Yes, but I believe we will see an increase in useful posts from people who would not otherwise participate. Another downside is the email addresses on the list will get spread around more which increase the change of them getting harvested by a spam mer. USENET people tend to get around this by using fake email addresses for USENET that can be modified by a human when the real address is needed. Mailing lists typically don't mask the email address, and since you can't fake an address if you wish to get email, everyone on the list will increase there changes of being spammed, but maybe only slightly. This isn't necessarily a big deal because several people have a separate mailing list address and/or have spam prevention in place. Wow this turned into a bigger message then I intended :-) On Wed, 10 Nov 2004 16:03:48 -0700, Net Virtual Mailing Lists <[EMAIL PROTECTED]> wrote: > Yeah.. I'm with you.. I don't really know what all of this is about - I > like the way the Postgres mailing list works as it is Are any of the > changes being discussed here going to change the content or how we > receive the mailing lists?.. > > .. The only change I've noticed is that in all the time of reading this > list I've not seen jerks posting forged messages like that > Certainly not a positive change, but I'm not sure it can be attributed to > what is going on... > > - Greg > > > > >??? As a longstanding reader of the pgsql- > >mailinglists, (including via news.postgresql.org on > >occasion), all I see is some outsiders trying to help > >us "fix" a problem that does not exist. And yes, I > >have read most of the messages that have passed by in > >these threads. After all that, I still don't see the > >benefit. > > > >Perhaps that is why these conversations have been > >carried on almost totally by people who do not post to > >the pgsql lists. > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster > ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[GENERAL] MIKE COX, EAT SHIT AND FUCK OFF YOU ASSHOLE. LEAVE us ALONE!
MIKE COX, EAT SHIT AND FUCK OFF YOU ASSHOLE. LEAVE us ALONE! Goutam Paruchuri ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] Important Info on comp.databases.postgresql.general
[EMAIL PROTECTED] ("Net Virtual Mailing Lists") wrote in
news:[EMAIL PROTECTED]:
> Yeah.. I'm with you.. I don't really know what all of this is about - I
> like the way the Postgres mailing list works as it is Are any of the
> changes being discussed here going to change the content or how we
> receive the mailing lists?..
As far as i think:
There will be no change to how the system is today. PostgreSQL mailing
lists is already gatewayed to news server all of the world. The process
which is ongoing only make the existing lists on usenet more approved and
therefor even more servers will caryy them.
Today we who want to access the lists through a news server need to connect
to news.postgresql.org or find another provider who support the
comp.databases.postgresql.*.
--
Rolf Østvik
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
[GENERAL] Can't insert date in field with foreign key
Hello list,
I'm a postgres-newbie with a maybe silly question.
I'm working on a SuSE-Linux 9.1 with PostgreSQL 7.4.6 with PostGIS 0.9.
My problem is, that I can't insert data into a table because I get the
error, that there is no corresponding value in the referenced field.
But when I query the referenced table with the value, I get a result.
Both fields are of the same type and length (varchar(10)).
1st Table:
CREATE TABLE "T_OEPNV_HST"
(
"HST_ID" serial,
"HST_NR" varchar(10),
"HST_NAME" varchar(256),
"HST_COORD" public.geometry,
CONSTRAINT "T_OEPNV_HST_pkey" PRIMARY KEY ("HST_ID"),
CONSTRAINT "T_OEPNV_HST_unr" UNIQUE ("HST_NR"),
CONSTRAINT "enforce_geotype_HST_COORD" CHECK geometrytype("HST_COORD")
= 'POINT'::text OR "HST_COORD" IS NULL,
CONSTRAINT "enforce_srid_HST_COORD" CHECK srid("HST_COORD") = 31467
) WITH OIDS;
2nd Table:
CREATE TABLE "T_OEPNV_HST_LIN" (
"HST_LIN_ID" serial primary key,
"HST_NR" varchar(10) references "T_OEPNV_HST" on update cascade,
"LIN_U_NAME" varchar(255) references "T_OEPNV_UNTERNEHMEN" ("U_NAME")
on update cascade,
"LIN_KAT" varchar(50) NOT NULL,
"LIN_NAME_O" varchar(50) NOT NULL,
"LIN_NAME_I" varchar(50) NOT NULL
);
The problem is related to the fields "HST_NR" in the two tables.
For Example:
insert into "T_OEPNV_HST_LIN" ("HST_NR", "LIN_U_NAME", "LIN_KAT",
"LIN_NAME_O", "LIN_NAME_I") values ('10001', 'Stadtwerke Marburg GmbH',
'Bus', 'C', '11103');
does not work while
select * from "T_OEPNV_HST" where "HST_NR"='10001';
returns
HST_ID | HST_NR | HST_NAME |HST_COORD
++--+--
23555 | 10001 | Afföller | SRID=31467;POINT(3483856.148 5632168.48)
(1 Zeile)
So, I can't understand, why I get the error, that I can't insert the
data into "T_OEPNV_HST_LIN" because there is no HAST_NR='10001' in
"T_OEPNV_HST".
I hope, someone can help...
Cheers,
Bjoern
--
momatec GmbH
www.momatec.de
---(end of broadcast)---
TIP 8: explain analyze is your friend
[GENERAL] pg_ctl and stderr
On 7.4.6 and earlier, we use apache's log rotation program as follows: pg_ctl start | rotatelogs ... If we have a configuration failure, say a bad parameter in postgresql.conf, we often don't quickly notice because it goes to stdout (into the log). It'd be nice if it went to stderr as well so we could see it without having to search the log, but that wouldn't work if we wanted to capture stderr in the logs (do normal ERROR messages go to stderr?). Just curious how folks make pg_ctl start-up failures obvious while also piping to apache rotatelogs? Ed ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [GENERAL] Lost databases
On Wed, 10 Nov 2004 08:11:01 -0800 (PST) Jeff Eckermann <[EMAIL PROTECTED]> wrote: > --- Liviu BURCUSEL <[EMAIL PROTECTED]> wrote: > > > Hi ! > > > > I'm in the ultimate state of dispair. Over the night > > some of my > > databases just disapeared. But they did not dissaper > > totally. I can > > still connect to them but I cannot dump them. When > > doing a "select * > > from pg_database" I see only 2 databases I hardly > > ever use (they are > > used once in a couple of mounths). Template0 and > > template1 are missing. > > All the databases that I currently use dissapeared! > > > > Please help me to restore the integrity of the > > system. I'm in dense fog > > here :( > > What Postgresql version is this? Your problem sounds > like "oid wraparound". There was a recent discussion > of this on the list; try the list archives to see what > was recommended in that case. > The Postgresql version is 7.4.1 Thanks. I'll look in the archive. Liviu ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[GENERAL] FUCK THAT ASSHOLE MIKE COX! HE loves SUCKING COCK!!!
FUCK THAT ASSHOLE MIKE COX! HE loves SUCKING COCK!!! Kevin Barnard ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[GENERAL] MIKE COX loves SUCKING DICKS and BALLS
MIKE COCKS loves SUCKING DICKS and BALLS FUCK THAT ASSHOLE MIKE COX! HE loves SUCKING COCK!!! Kevin Barnard ---(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: [GENERAL] MIKE COX, EAT SHIT AND FUCK OFF YOU ASSHOLE. LEAVE us ALONE!
This would be another forgery. In case anyone's curious, this looks like the work of the well known net.kook, Steve Young <[EMAIL PROTECTED]>. He seems to be a well known personality on news.groups (and alt.usenet.kooks). He has a strange obsession with newsgroup charters and he's been forging votes on newsgroup creation CFVs recently. Search for "steve young lidya.net" on groups.google.com for some other examples of his work. You'll have to block at least mailout01.ims-firmen.de [213.174.32.96] as well. And probably sneakemail.com's servers as well, a remailer he seems to be fond of. I don't know if that'll stop him though. In all likelihood he'll get tired of this once the newsgroup administrivia has passed and move on to harass other people. Perhaps he'll get bored of it already once he sees that we know who it is. -- greg ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
