Re: [ADMIN] psql shell return codes - checking if database exists

Perhaps the grep solution will only provide an accurate response if the database name is not a substring of some other database name. In other words, if one were to attempt to confirm that database prod10 exists- they might execute (per the suggestion): psql --list | grep prod10 But, the result c

[ADMIN] Logging issue

I just upgraded to PostgreSQL 9.0.2. I was told there was a change made to logging in this version such that when a prepared statement is executed and there is an error instead of seeing $# in the SQL logs you would see the actual values. I am still seeing the $# not the values. Is there some

Re: [ADMIN] tsvector limitations

Greg Williamson wrote: > Try trolling texts at the Internet Archive (archive.org) -- lots > of stuff that has been rendered into ASCII ... Government > documents and the like from all periods; novels and the like that > are no longer under copyright, so lots of long classics. > >

Re: [ADMIN] tsvector limitations

When this discussion first started, I immediately thought about people who full text index their server's log files. As a test I copied /var/log/messages to $PGDATA and then used the same pg_read_file() function you mentioned earlier to pull the data into a column of type text. The original fil

Re: [ADMIN] tsvector limitations

"Mark Johnson" writes: > When this discussion first started, I immediately thought about people > who full text index their server's log files. As a test I copied > /var/log/messages to $PGDATA and then used the same pg_read_file() > function you mentioned earlier to pull the data into a column of

Re: [ADMIN] tsvector limitations

On Wed, 15 Jun 2011, Tom Lane wrote: and not an actual document.) Any discussion of required tsvector sizes that doesn't account for the actual, nonlinear scaling behavior isn't worth the electrons it's printed on. Tom, you're my hero ! Regards, Oleg __

Re: [ADMIN] tsvector limitations

Hi Tom, My limited testing indicates tsvector size has an approximately linear (binomial) correlation with "number of unique words", and "word count". Presumably your "nonlinear" remark was (correctly) directed at the correlation between file size and tsvector size. I found that: VS=UW*AWS+2*WC+5

Re: [ADMIN] tsvector limitations

Tim writes: > My limited testing indicates tsvector size has an approximately linear > (binomial) correlation with "number of unique words", and "word count". Yes, it would be linear in the number of unique words (assuming the average word length stays constant). It's not linear in word count, b

[ADMIN] could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

Hi, We have postgresql9.0 in our Linux server. We are continously getting "could not open temporary statistics file "pg_stat_tmp/pgstat.tmp": No such file or directory" message in the db log file.We have data/pg_stat_tmp directory in, but pgstat.tmp file is not ppresent in this directory.Can someon

Re: [ADMIN] could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

I don't know but I would try this first: touch pg_stat_tmp/pgstat.tmp chmod 0777 pg_stat_tmp/pgstat.tmp ls -halZ pg_stat_tmp On Thu, Jun 16, 2011 at 1:28 AM, bakkiya wrote: > Hi, > We have postgresql9.0 in our Linux server. We are continously getting > "could > not open temporary statistics file

Re: [ADMIN] could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

On Thu, Jun 16, 2011 at 6:28 AM, bakkiya wrote: > We have postgresql9.0 in our Linux server. We are continously getting "could > not open temporary statistics file "pg_stat_tmp/pgstat.tmp": No such file or > directory" message in the db log file.We have data/pg_stat_tmp directory in, > but pgstat

[ADMIN] Re: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

postgresql/data/pg_stat_tmp> df -h . FilesystemSize Used Avail Use% Mounted on /dev/xvdb1197G 16G 171G 9% /pub postgresql/data/pg_stat_tmp> touch a novell@s210:/pub/var/opt/novell/sentinel/3rdparty/postgresql/data/pg_stat_tmp> ls -rtl total 96 -rw--- 1 novell nove

Re: [ADMIN] Re: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

On Thu, Jun 16, 2011 at 7:44 AM, bakkiya wrote: > Space,permission are not an issue. Then presumably you have your stats_temp_directory parameter set to a path where that is not true. --  Simon Riggs   http://www.2ndQuadrant.com/  PostgreSQL Development, 24x7 Support, Training

Re: [ADMIN] Re: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/2011 08:44 AM, bakkiya wrote: > > postgresql/data/pg_stat_tmp> touch a > novell@s210:/pub/var/opt/novell/sentinel/3rdparty/postgresql/data/pg_stat_tmp> > ls -rtl > total 96 > -rw--- 1 novell novell 91898 2011-06-15 23:36 pgstat.stat > -r

[ADMIN] Re: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp"

No, we run postgres with the novell user only. -- View this message in context: http://postgresql.1045698.n5.nabble.com/could-not-open-temporary-statistics-file-pg-stat-tmp-pgstat-tmp-tp4493683p4493834.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-a