[ADMIN] These Lists Are Being Cut To FOUR
Hello. My name is Mike Cox. I am in charge of the changing of these postgresql lists. I have decided that we are going to drop most of the lists from the vote. We will only be making 4 lists into real Usenet newsgroups if we win the election. The rest of the lists are crap and they take up too much fucking room. Marc was an asshole for stealing BIG8 newsgroup names without voting. He is an irresponsible piece of shit scumbag cock-licking anus-eating foreskin-sniffing motherfucking faggot. He has an ego the size of Dolly Parton's tits. Be sure to vote yes on all four of these lists or every list will be removed. Your support is most appreciated! Mike Cox [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
[ADMIN] How to support German, French and other characters.
Hi to all, We are using pgsql as a "multilanguage" database. But I noticed yesterday a strange problem with the german umlaut characters. I cannot convert the in upper case in lowercase. Probably there are also other bad functionalities. Now. I searched the internet for answers but they were not quite exact, so I could't find a solution. We use ASCII encoding for the database, but I tried the Latin1 -> Latin 10 and the behavior is the same. In some forums there is written something about some "locale" setting... etc etc. What settings do I have to make so that we won't have these problems in the future. We intend to work with French characters also, and in the future with Hungarian. As system the pgsql is v.7.4 running on a Suse 9.1 machine. The locale command gives me: linz:/var/lib/pgsql/data # localeLANG=LC_CTYPE=en_US.UTF-8LC_NUMERIC="POSIX"LC_TIME="POSIX"LC_COLLATE="POSIX"LC_MONETARY="POSIX"LC_MESSAGES="POSIX"LC_PAPER="POSIX"LC_NAME="POSIX"LC_ADDRESS="POSIX"LC_TELEPHONE="POSIX"LC_MEASUREMENT="POSIX"LC_IDENTIFICATION="POSIX"LC_ALL= Thank you in advance. Andy.
[ADMIN] how do you run postgres without dns server
I have a database on a machine that does not know what localhost is. Yes, I have 127.0.0.1, but I can't resolve localhost to it. I don't want to start a caching dns, and don't want to change resolve.conf. Upon starting, postgres gives error cannot bind to localhost. then starts accepting connections to 127.0.0.1 normaly. So, why does postgres try to resolve localhost in the first place? Because of this error pg_autovacuum does not start. -- Hi! I'm your friendly neighbourhood signature virus. Copy me to your signature file and help me spread! pgp5bhUOSID29.pgp Description: PGP signature
Re: [ADMIN] how do you run postgres without dns server
localhost should be defined in your hosts file, which in most unixoid environments is /etc/hosts. It is not an error. Hal On Wed, 10 Nov 2004, Ivan Dimitrov wrote: > I have a database on a machine that does not know what localhost is. Yes, I > have 127.0.0.1, but I can't resolve localhost to it. I don't want to start a > caching dns, and don't want to change resolve.conf. Upon starting, postgres > gives error cannot bind to localhost. then starts accepting connections to > 127.0.0.1 normaly. > So, why does postgres try to resolve localhost in the first place? Because of > this error pg_autovacuum does not start. > -- > > > Hi! I'm your friendly neighbourhood signature virus. > Copy me to your signature file and help me spread! > ---(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: [ADMIN] how do you run postgres without dns server
Yes, it is there 127.0.0.1localhost but when i strace postmaster on startup it never looks in /etc/hosts На 10.11.2004 12:05 вие написахте: > localhost should be defined in your hosts file, which in most unixoid > environments is /etc/hosts. It is not an error. > > Hal > > On Wed, 10 Nov 2004, Ivan Dimitrov wrote: > > I have a database on a machine that does not know what localhost is. Yes, > > I have 127.0.0.1, but I can't resolve localhost to it. I don't want to > > start a caching dns, and don't want to change resolve.conf. Upon > > starting, postgres gives error cannot bind to localhost. then starts > > accepting connections to 127.0.0.1 normaly. > > So, why does postgres try to resolve localhost in the first place? > > Because of this error pg_autovacuum does not start. > > -- > > > > > > Hi! I'm your friendly neighbourhood signature virus. > > Copy me to your signature file and help me spread! -- Hi! I'm your friendly neighbourhood signature virus. Copy me to your signature file and help me spread! pgpNbs07BHVOh.pgp Description: PGP signature
Re: [ADMIN] These Lists Are Being Cut To FOUR
Hi, > Hello. My name is Mike Cox. I am in charge of the changing of these > postgresql lists. I have decided that we are going to drop most of the > lists from the vote. We will only be making 4 lists into real Usenet > newsgroups if we win the election. The rest of the lists are crap and > they take up too much fucking room. Marc was an language>. Be sure to vote yes on all four of these lists or every list > will be removed. Please grow up and learn to use decent language and arguments to make your point... > Your support is most appreciated! Kicking this guy off the lists would be very much appreciated... Sander. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] These Lists Are Being Cut To FOUR
On Wed, 2004-11-10 at 07:59 +, Mike Cox wrote: > Hello. My name is Mike Cox. I think this offensive mail was forged; please do not attribute it to the real Mike Cox unless he affirms it. Here is the first Received header at svr1.postgresql.org; and note the message id also contains the string mail3.lidya.net: Received: from mail3.lidya.net (unknown [212.79.114.20]) by svr1.postgresql.org (Postfix) with SMTP id 4E5173A41A7 for <[EMAIL PROTECTED]>; Wed, 10 Nov 2004 08:00:57 + (GMT) Received: (qmail 31275 invoked by uid 398); 10 Nov 2004 07:59:12 - Date: 10 Nov 2004 07:59:12 - Message-ID: <[EMAIL PROTECTED]> To: List <[EMAIL PROTECTED]> Subject: [ADMIN] These Lists Are Being Cut To FOUR From: Mike Cox <[EMAIL PROTECTED]> lidya.net is a Turkish site. -- 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: [ADMIN] how do you run postgres without dns server
On Wed, 2004-11-10 at 12:15 +0200, Ivan Dimitrov wrote: > Yes, it is there > 127.0.0.1localhost > but when i strace postmaster on startup it never looks in /etc/hosts Look at the "hosts:" line in /etc/nsswitch.conf. It needs to have the word "files" in there. -- 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 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [ADMIN] nscd [was] how do you run postgres without dns server
Yes that is true too. I've checked it all. It apears that postgres tries to resolve only through dns'...:( I think that the problem is in the postgresql, but I can't reproduce the problem anymore, because I was forced to install a caching dns server, and I'm not allowed to play with it anymore (business must run). The nscd problem: I didn't post this before, because I thik this is not a postgres related problem, but after a few hours playing with it I couldn't fix the problem I have nscd + pgsql backend I have passwd: compat [NOTFOUND=continue SUCCESS=return] pgsql group: compat [NOTFOUND=continue SUCCESS=return] pgsql in /etc/nsswitch.conf The logic of this, from what I could understand from the documentation is: "Look in the standart files (/etc/passwd, /etc/group)" for username and groups, if not found, search in pgsql databasee, else return successfull" The problem is that when I stop the database and I try to `id realuser` it gives: # id root Could not connect to database The system is Debian sarge with packages: nscd 2.3.2.ds1-18 libnss-pgsql1 1.0.2-1.2 postgresql 7.4.5-3 На 10.11.2004 16:08 Oliver Elphick написа: > On Wed, 2004-11-10 at 12:15 +0200, Ivan Dimitrov wrote: > > Yes, it is there > > 127.0.0.1localhost > > but when i strace postmaster on startup it never looks in /etc/hosts > > Look at the "hosts:" line in /etc/nsswitch.conf. It needs to have the > word "files" in there. -- Hi! I'm your friendly neighbourhood signature virus. Copy me to your signature file and help me spread! pgpcEPAARk313.pgp Description: PGP signature
[ADMIN] Bad Timestamp Error with COPY
I am new to Postgresql. I'm trying to load tables from SQLServer bcp export, comma delimited. I'm loading datetime datatype into timestamp. I've loaded one table successfully and failed on others with the same error: Bad timestamp external representation ''. The table that loaded successfully had datetime data in the exact same format asthis one. I have taken this file apart and successfully loaded it one or two fields at a time, including the datetime fields (into timestamp) but it will not load as is. I've changed the delimiter to \t and tried \. at the end. I've changed the field types from timestamp to char(25) and it loaded fine. I tried to create another table and cast to timestamp from char. That's not allowed. Any help will be appreciated. Here is the version, the table description, the COPY stmt with error, and the input file(it's only one row). ems=# select version();PostgreSQL 7.3.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1 (SuSE Linux) ems=# \d edadvisor_char;Table "public.edadvisor_char" advisor1 | character varying(60)whenent1 | timestamp without time zone advisor2 | character varying(60) whenent2 | timestamp without time zone advisor3 | character varying(60) whenent3 | timestamp without time zone advkey | character(1) whenchange | timestamp without time zone bhhwhenchange | timestamp without time zone bmhwhenchange | timestamp without time zone kmcwhenchange | timestamp without time zone merwhenchange | timestamp without time zone sjhwhenchange | timestamp without time zone ems=# copy edadvisor_char from '/home/xx/test_data.txt' using delimiters ',';ERROR: copy: line 1, Bad timestamp external representation ''ems=# ** test_data.txt Off E.D. Rotation,2004-09-01 00:00:01.000,testing,2004-09-01 00:00:06.000,,,1,2004-09-02 12:56:43.000,2004-08-05 15:13:10.000,2004-08-05 14:29:01.000,2004-08-05 14:57:32.000,2004-08-05 13:49:46.000,2004-08-06 14:05:07.000
Re: [ADMIN] Bad Timestamp Error with COPY
On Wed, 10 Nov 2004, Sharon Schooley wrote: > I am new to Postgresql. I'm trying to load tables from SQLServer bcp > export, comma delimited. I'm loading datetime datatype into timestamp. > I've loaded one table successfully and failed on others with the same > error: > Bad timestamp external representation ''. > > The table that loaded successfully had datetime data in the exact same > format as this one. I have taken this file apart and successfully loaded > it one or two fields at a time, including the datetime fields (into > timestamp) but it will not load as is. I've changed the delimiter to \t > and tried \. at the end. I've changed the field types from timestamp to > char(25) and it loaded fine. I tried to create another table and cast to > timestamp from char. That's not allowed. > > Any help will be appreciated. > > Here is the version, the table description, the COPY stmt with error, > and the input file(it's only one row). > > ems=# select version(); > PostgreSQL 7.3.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1 (SuSE > Linux) > > ems=# \d edadvisor_char; > Table "public.edadvisor_char" > > advisor1 | character varying(60) > whenent1 | timestamp without time zone > advisor2 | character varying(60) > whenent2 | timestamp without time zone > advisor3 | character varying(60) > whenent3 | timestamp without time zone > advkey | character(1) > whenchange | timestamp without time zone > bhhwhenchange | timestamp without time zone > bmhwhenchange | timestamp without time zone > kmcwhenchange | timestamp without time zone > merwhenchange | timestamp without time zone > sjhwhenchange | timestamp without time zone > > > ems=# copy edadvisor_char from '/home/xx/test_data.txt' using delimiters > ','; > ERROR: copy: line 1, Bad timestamp external representation '' > ems=# > > ** test_data.txt Breaking it up: advisor1 > Off E.D. Rotation, whenent1 > 2004-09-01 00:00:01.000, advisor2 > testing, whenent2 > 2004-09-01 00:00:06.000, advisor3 >, whenent3 >, whenent3 is getting an empty string for its date and that's not allowed. If you want empty strings in the file to be treated as null, you can use NULL AS ''. ---(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: [ADMIN] nscd [was] how do you run postgres without dns server
Do you got "hosts: files dns" in your nsswitch.conf? Otherwise , /etc/hosts won't be used. - # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis -- Regards Simon Chen. -- Original Message --- From: Ivan Dimitrov <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Wed, 10 Nov 2004 17:19:47 +0200 Subject: Re: [ADMIN] nscd [was] how do you run postgres without dns server > Yes that is true too. I've checked it all. It apears that postgres > tries to resolve only through dns'...:( > > I think that the problem is in the postgresql, but I can't reproduce > the problem anymore, because I was forced to install a caching dns > server, and I'm not allowed to play with it anymore (business must > run). > > The nscd problem: > I didn't post this before, because I thik this is not a postgres > related problem, but after a few hours playing with it I couldn't > fix the problem I have nscd + pgsql backend I have passwd: > compat [NOTFOUND=continue SUCCESS=return] pgsql group: > compat [NOTFOUND=continue SUCCESS=return] pgsql > > in /etc/nsswitch.conf > The logic of this, from what I could understand from the > documentation is: "Look in the standart files (/etc/passwd, > /etc/group)" for username and groups, if not found, search in pgsql > databasee, else return successfull" > > The problem is that when I stop the database and I try to `id > realuser` it gives: > # id root > Could not connect to database > > The system is Debian sarge with packages: > nscd 2.3.2.ds1-18 > libnss-pgsql1 1.0.2-1.2 > postgresql 7.4.5-3 > > Íà 10.11.2004 16:08 Oliver Elphick íàïèñà: > > On Wed, 2004-11-10 at 12:15 +0200, Ivan Dimitrov wrote: > > > Yes, it is there > > > 127.0.0.1localhost > > > but when i strace postmaster on startup it never looks in /etc/hosts > > > > Look at the "hosts:" line in /etc/nsswitch.conf. It needs to have the > > word "files" in there. > > -- > > Hi! I'm your friendly neighbourhood signature virus. > Copy me to your signature file and help me spread! --- End of Original Message --- ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[ADMIN] request for feature - mixed case name handling
I guess this may or may not belong here, but may I ask people's opinion on requesting an improvement. I have a database with mixed case table names (like "MixedCaseTable") and column names (like "MixedCaseColumn"). I have many tables so would like to use descriptive names, so chose to use mixed case names instead of using _ to separate words. It is good for readability and complex naming, but I have these problems. 1. Some automated development tools, including Dreamweaver, Netbeans, dbVisualizer and other tools cannot work with the mixed case names. I cannot insert a recordset, e.g. I think between those tools-postgresql (like in phakt) or tools-jdbc-postgresql (unlike jdbc, odbc seems to handle it OK), there are different expectations. For example, in Dreamweaver with jsp/jdbc, it gets the mixed case table/column names correctly but "cannot find table" if I try to "view data". Recordsets and server behaviors do not work correctly. 2. On psql, the tab (auto)completion is a convenient feature for long names. However, it doesn't work with mixed case names. With a table name like "aTableName", if I do [select * from aTableN] it gives me [select * from aTableName]. It gets completed OK. But when I run it, I get an error "table atablename not found" since the autocompletion doesn't add "" around the table names and the name subsequently gets treated as a lowercase name, so I have to add quotes around manually. If I do [select * from "aTableN], I get no autocompletion. 3. I know the official answer to this problem is that postgresql is SQL92 compliant in that "unquoted names are case insensitive". But I also saw some people in this list having problems with this handling of mixed case. I would like to submit a request, or whatever is appropriate, asking the development team to solve this problem. I wonder what it takes for it to be a valid request? This problem is not so much of developer's lazyness or ignorance, but more of the general assumptions hidden in the automated development tools. We can go after the tool vendors one by one and shout and scream for accommodation of postgresql's handling of the mixed case names, but we have one postgresql and so many development tool vendors so it doesn't seem to be the right way. For your reference, mysql recognizes mixed case identifiers and keeps it across the board without quotes. Dreamweaver works fine with mysql on mixed case names. As someone on this list suggested a while back, if this "compliance with SQL92 case insensitivity" can be turned on or off based on users' preference, it would be really great. If anyone in this list is facing a similar problem, I would like to ask for opinions on this list. Although I spoke of inconveniences, let me say I deeply appreciate the efforts of the developers. Thanks. Ben Kim Database Developer/Systems Administrator College of Education Texas A&M University ---(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
