于 2013/9/17 0:02, Kevin Grittner 写道:
Possibly. As I said before, I think the symptoms might better fit a
situation where the table in need of VACUUM was a shared table and it
just happened to mention db1 because that was the database it was
scanning at the time. (Every database includes the
于 2013/9/16 1:31, Kevin Grittner 写道:
There's your problem. You left so little space between when
autovacuum would kick in for wraparound prevention (2 billion
transactions) and when the server prevents new transactions in
order to protect your data (2 ^ 31 - 100 transactions) that
于 2013/9/15 1:06, Kevin Grittner 写道:
Rural Hunter ruralhun...@gmail.com wrote:
Why in the world would you want to use VACUUM FULL in this circumstance?
the db name in the error message wrong?
I just googled around and found the solution. What's the other option?
There are two possibilities
I really hate the error permission denied for sequence x when I
grant on a table but forget to grant additionally on the related
sequence to users. Can the permission of table and related sequences be
merged?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
于 2013/6/19 17:47, Szymon Guz 写道:
On 19 June 2013 11:35, Rural Hunter ruralhun...@gmail.com
wrote:
I really
hate the error "permission denied for sequence x" when
I grant on a table
Yes, that's also an acceptable
solution.
于 2013/6/20 3:48, Craig James 写道:
On Wed, Jun 19, 2013 at 2:35 AM, Rural
Hunter ruralhun...@gmail.com
wrote:
I really hate the error "permission denied for seq
Hi,
I encounter the same issue often: Granted update/insert to an user but
forgot to grant it on the related sequence. It's hard to understand that
an user has write access on table but not on necessary sequences. I
think the grant on tables should cascade to related sequences. What do
you
I'm doing the same thing. In my case, the vacuum part on parent is very
quick while analyzing takes a bit longer since it runs rough analyzes
all children tables. You can see the behavior by analyze verbose.
Maybe the bigger part of your vacuum/analyze is on analyze so that you
are seeing this
于 2012/12/12 13:44, Sergey Konoplev 写道:
On Tue, Dec 11, 2012 at 9:39 PM, Rural Hunter ruralhun...@gmail.com wrote:
Great. It works now. Thanks a lot for your instant help!
You are welcome.
Thanks for your feedback and sorry for this bugs. I have noted down
this issue with password and planned
Hi Sergey,
I downloaded pgtoolkit-v1.0beta3-fatscripts.tar.gz and tested it. I got
error when trying this:
./pgcompactor -a -u
DatabaseChooserError Can not find an adapter. at
/loader/0x1c26f18/PgToolkit/DatabaseChooser.pm line 63.
./pgcompactor -d testdb -u
DatabaseChooserError Can not find
, 2012 at 7:40 PM, Rural Hunter ruralhun...@gmail.com wrote:
I downloaded pgtoolkit-v1.0beta3-fatscripts.tar.gz and tested it. I got
error when trying this:
./pgcompactor -a -u
DatabaseChooserError Can not find an adapter. at
/loader/0x1c26f18/PgToolkit/DatabaseChooser.pm line 63.
./pgcompactor -d
于 2012/12/12 12:24, Sergey Konoplev 写道:
On Tue, Dec 11, 2012 at 7:57 PM, Rural Hunter ruralhun...@gmail.com wrote:
I do have psql installed. I'm on the db server.
$ psql
psql.bin (9.1.0)
Type help for help.
postgres=# \q
$ ./pgcompactor -a -u
DatabaseChooserError Can not find an adapter
于 2012/12/12 12:47, Sergey Konoplev 写道:
On Tue, Dec 11, 2012 at 8:30 PM, Rural Hunter ruralhun...@gmail.com wrote:
No. I was running it with another db super user. should it only be run by
postgres?
$ echo 'SELECT 1;' | psql -q -A -t -X -U postgres -P null=NULL
Password for user postgres:
1
于 2012/12/12 13:31, Sergey Konoplev 写道:
Yes. It is known bug and it is fixed in the future (not yet released) version.
See the attachment.
Great. It works now. Thanks a lot for your instant help!
--
Sergey Konoplev
Database and Software Architect
http://www.linkedin.com/in/grayhemp
Phones:
Hi,
I'm on 9.1.3. I set auto vacuum off for some tables. I noticed one
thing: when I run manual analyze on parent table, It seems the children
tables are also analyzed. Here is the analyze log:
INFO: analyzing public.table_parent
INFO: table_parent: scanned 0 of 0 pages, containing 0 live
Got it. Thanks.
于2012年11月8日 23:21:33,Albe Laurenz写到:
Rural Hunter wrote:
I'm on 9.1.3. I set auto vacuum off for some tables. I noticed one
thing: when I run manual analyze on parent table, It seems the
children
tables are also analyzed. Here is the analyze log:
INFO: analyzing
or set the 'PGPORT' env variable.
于 2012/9/17 14:29, Devrim GÜNDÜZ 写道:
Hi,
On Mon, 2012-09-17 at 11:55 +0530, himanshu.joshi wrote:
I have changed the default port of postgres in file
postgresql.conf from 5432 to another four digit port which was not
assigned to any one else. After the
于 2012/9/16 2:06, Bruce Momjian 写道:
On Sat, Sep 15, 2012 at 11:40:06AM +0800, Rural Hunter wrote:
The check is to make sure that once we have created all the user schema
details in the new cluster, that there are the same number of objects in
the new and old databases.
Obviously
于2012年9月14日 22:26:16,Bruce Momjian写到:
On Fri, Sep 14, 2012 at 01:43:30PM +0800, Rural Hunter wrote:
I am trying to test the upgrade from my 9.1.3 db to 9.2 on ubuntu
10.10 server. I got error below when run the pg_upgrade command.
What can I do for this?
$ /opt/PostgreSQL/9.2/bin/pg_upgrade -b
I am trying to test the upgrade from my 9.1.3 db to 9.2 on ubuntu 10.10
server. I got error below when run the pg_upgrade command. What can I do
for this?
$ /opt/PostgreSQL/9.2/bin/pg_upgrade -b /opt/PostgreSQL/9.1/bin -B
/opt/PostgreSQL/9.2/bin -d /raid/pgsql -D /raid/pg92data
Performing
Thanks!
于 2012/9/7 20:20, Sergey Konoplev 写道:
On Fri, Sep 7, 2012 at 9:44 AM, Rural Hunter ruralhun...@gmail.com wrote:
base_20120902.tar.gz
27781958.tar.gz
27781959.tar.gz
Now I want to restore it on another server with only one disk. I'm confused
how to handle those tablespace files
turn auto vacuum off for those tables.
于 2012/9/11 4:30, David Morton 写道:
We have many large tables which contain static historical data, they
are auto vacuumed on a regular basis (sometimes to prevent wraparound)
which i suspect causes a few annoying side effects:
- Additional WAL file
Hi,
I have a database with several tablespaces on different disks and
backup-ed it with pg_basebackup. I have theses files:
base_20120902.tar.gz
27781958.tar.gz
27781959.tar.gz
Now I want to restore it on another server with only one disk. I'm
confused how to handle those tablespace files.
[192.168.1.8] ([116.226.69.188])
by mx.google.com with ESMTPS id sr3sm15887340pbc.44.2012.08.27.18.54.57
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 27 Aug 2012 18:54:58 -0700 (PDT)
Message-ID: 503c24ec.3030...@gmail.com
Date: Tue, 28 Aug 2012 09:54:52 +0800
From: Rural Hunter ruralhun
v9.1.3 on Ubuntu 10.04 server. I have one table which has frequent
insert and weekly deletion, no update. Recently, I found the auto vacuum
on the toast table of it almost running all the time. each run took
around 1 hour. I don't think there are so many inerts so that it reaches
the auto
于 2012/4/17 18:06, Albe Laurenz 写道:
Rural Hunter wrote:
That's probably the problem - it seems to emit something that is
not proper UTF-8 sometimes.
Do you get the error if you try Chinese settings without nlpbamboo?
How can I do this? The Chinese processing is provided by nlpbamboo.
--
Sent
2012/4/16 16:31, Albe Laurenz 写道:
Rural Hunter wrote:
My db is in utf-8, I have a row in my table say tmp_article and I
wanted
to generate ts_vector from the article content:
select to_tsvector(content) from tmp_article;
But I got this error:
ERROR: invalid byte sequence for encoding UTF8
3ae9b9b0e79cbce4b8aae882a1e699bae883bde8b79fe8b8aae7b3bbe7bb9fe68f90e4be9befbc8ce6aca2e8bf8ee8bdace8bdbdefbc8ce8afb7e6b3a8e6988ee587bae5a484e380820ae79bb8e585b3e696b0e997bbefbc9
a0ae8b4a3e4e7bc96e8be91efbc9ae5bb96e6b3bde5878c
于 2012/4/16 21:34, Albe Laurenz 写道:
Please don't top post.
Rural Hunter wrote:
My db is in utf-8, I have a row in my
still doesn't work.
db=# set client_encoding='SQL_ASCII' ;
SET
db=# select to_tsvector(content) from tmp_article;
ERROR: invalid byte sequence for encoding "UTF8": 0xf481
2012/4/15 1:38, raghu ram :
On Sat, Apr 14, 2012 at 9:31
My db is in utf-8, I have a row in my table say tmp_article and I wanted
to generate ts_vector from the article content:
select to_tsvector(content) from tmp_article;
But I got this error:
ERROR: invalid byte sequence for encoding UTF8: 0xf481
I am wondering how this could happen. I think if
=# select to_tsvector(content) from tmp_article;
ERROR: invalid byte sequence for encoding "UTF8": 0xf481
2012/4/14 10:15, raghu ram :
2012/4/14 Rural Hunter ruralhun...@gmail.com
My db is in utf-8, I have a row in my table say tmp_article
I'm trying to set up a standby server. Both the primary and standby
servers are on latest version 9.1.3 on ubunt server 10.10. So far I
tried to init the setup 2 times but both failed after the replication
running for some time. what can I do to fix this? The log on the standby
is shown below:
yes, I understand that. but is it worth mentioning in the doc?
于2012年3月12日 22:11:16,Kevin Grittner写到:
Rural Hunterruralhun...@gmail.com wrote:
triggers are not shared between parent and child tables. is it
true?
Yes.
You can use the same trigger *function* for more than one trigger
hmmif you ask me, I would like to suggest add this part in the
fisrt step(create the master table) of 5.9.2 of this doc:
http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html
The doc mentions here that there is no point to define
indexes/constraints on parent table. But it didn't
I implemented table partition recently and found that the tiggers on
parent table are not working any more, except the before insert trigger
which redirects data to children table. The after insert/update triggers
are not working now. I understand the after insert trigger may not
working since
I want to separate my indexes into a tablespace which resides on a raid0
disk for fast r/w access. Is it safe? what I mean is, if the raid0 disk
is damaged, is it easy to recover the indexes by just recreating those
indexes?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To
thanks. temporarily not having the indexes should be fine to me.
于2012年3月5日 23:53:52,Nicholson, Brad (Toronto, ON, CA)写到:
-Original Message-
From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-
ow...@postgresql.org] On Behalf Of Rural Hunter
Sent: Monday, March 05, 2012 8:28 AM
My db is in UTF-8 encoding. When I tried to generate gist index for some
rows I got the strange error:
select to_tsvector('chinesecfg',content) from article where
article_id=23834922;
ERROR: invalid byte sequence for encoding UTF8: 0xf480
However, select content from article where
yes, it's truncated. the full sql is like this:
update article set
tm_update=$1,rply_cnt=$2,read_cnt=$3,tm_last_rply=$4 where
title_hash=$5
the title_hash is unique.
I dig another case more and found something interesting. it's actually
waiting for a lock of type transactionid. I ran the
well, thanks. I checked the application and found there was a bug
causing many queries were updating the same row. However, those updates
are just single statement, no multi-statement transaction involved. So
I still have this question:
same statement A,B,C,D update same row. The start order is
hmmno I didn't do anything. is the lock priority decided by OS not
the DB? I'm confused here. B/C/D started several mins later than A here
while the update statement takes no more than 1 second. of coz there
are hundreds of connections trying to acquire the lock during that
time.
I'm seeing connection hang issue these days. many concurrent
connections are hanging on db. They basically do the same thing:
update different rows in same table. The sql itself should run very
fast as it's updating just one row based on an unique key. I though
it might
I noticed there were some statistics for triggers in pgAdmin III GUI,
such as total execution count and execution time. But they are all
empty. is there any way to enable those statistics?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
well, is pgsql capable to parse shell variables in postgresql.conf?
anway you should check your master log. If it can not archive the wal,
there will be errors reported in it.
于2011年12月16日 2:02:03,Khusro Jaleel写到:
Hello, I'm trying out a simple example from the Postgresql 9
Administration
Hi,
I'm trying to set up a hot standby server with both primary and standby
are at latest version 9.1.2. I used pg_basebackup to create the backup
and there was no problem in the log:
NOTICE: pg_stop_backup complete, all required WAL segments have been
archived
-rw-r--r-- 1 postgres
I have the same confusion...
于 2011/11/30 2:34, Rob Richardson 写道:
Very naïve question here: Why would you want to save the data from the first
insert?
I thought the purpose of a transaction was to make sure that all steps in the
transaction executed, or none of them executed. If Oracle
I am looking for something like a string hash function to order a string
cloumn randomly.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
great, thanks. is there any other system function besides string
functions?
于2011年9月27日 17:37:29,Thomas Kellerer写到:
Rural Hunter, 27.09.2011 11:00:
I am looking for something like a string hash function to order a
string cloumn randomly.
It's all in the manual ;)
http
/static/functions.html
--
Ian.
On Tue, Sep 27, 2011 at 10:44 AM, Rural Hunterruralhun...@gmail.com wrote:
great, thanks. is there any other system function besides string functions?
于2011年9月27日 17:37:29,Thomas Kellerer写到:
Rural Hunter, 27.09.2011 11:00:
I am looking for something like a string
Hi,
I set up an warm standby server which fetches WAL logs from a remote
server. It has been working very well. But today, I was editing the
restore script(which is set as the restore_command) with vi. Just right
after I saved the script, I noticed suddenly the standby server
terminated. I
Got it. thanks.
于2011年9月21日 1:31:09,Kevin Grittner写到:
Rural Hunterruralhun...@gmail.com wrote:
I set up an warm standby server which fetches WAL logs from a
remote server. It has been working very well. But today, I was
editing the restore script(which is set as the restore_command)
with vi.
This is my env:
postgres@backup:~$ env
MANPATH=:/opt/PostgreSQL/9.1/share/man
SHELL=/bin/bash
TERM=linux
USER=postgres
LD_LIBRARY_PATH=/opt/PostgreSQL/9.1/lib/
PGPORT=3500
yes, tried that too and same thing happened.
于2011年9月18日 17:09:25,Richard Shaw写到:
Tried adding the path to ldconfig rather than redefining ld_library_path?
On 18 Sep 2011, at 09:03, Scott Marlowescott.marl...@gmail.com wrote:
Wow, you got me.
On Sun, Sep 18, 2011 at 12:56 AM, Rural
11:20 postgresql
于2011年9月18日 21:58:17,Peter Eisentraut写到:
On sön, 2011-09-18 at 14:56 +0800, Rural Hunter wrote:
This is my env:
postgres@backup:~$ env
MANPATH=:/opt/PostgreSQL/9.1/share/man
SHELL=/bin/bash
TERM=linux
USER=postgres
LD_LIBRARY_PATH=/opt/PostgreSQL/9.1/lib/
PGPORT=3500
LS_COLORS
in the final release. So my problem
is resolved. Thank you all.
于 2011/9/18 23:25, Peter Eisentraut 写道:
On sön, 2011-09-18 at 22:41 +0800, Rural Hunter wrote:
I didn't install anything else there:
(for a very small value of anything else)
It looks like you have some version of libncurses
I installed pgsql 9.1 on Ubuntu server(10.10). Now I have a problem with
the required env variable LD_LIBRARY_PATH. If I do not set this, I can
not use some pg tools such as pg_dump, createuser...etc. If I set this
variable, my term gets warning unknown terminal type for some linux
commands
I'm making a base backup with 9.1rc by following 24.3.3 in manual:
http://www.postgresql.org/docs/9.1/static/continuous-archiving.html
1. SELECT pg_start_backup('label');
2. perform file system backup with tar
3. SELECT pg_stop_backup();
But when I was performing step 2, I got warning from tar
OK, thank you.
于2011年9月11日 1:30:48,Guillaume Lelarge写到:
On Sun, 2011-09-11 at 01:19 +0800, Rural Hunter wrote:
I'm making a base backup with 9.1rc by following 24.3.3 in manual:
http://www.postgresql.org/docs/9.1/static/continuous-archiving.html
1. SELECT pg_start_backup('label');
2. perform
: invalid byte sequence for encoding
UTF8: 0xe5272c
2011-09-01 11:27:15 CST ERROR: invalid byte sequence for encoding
UTF8: 0xe5a427
What could be the cause of that?
于 2011/8/30 9:29, Rural Hunter 写道:
Thank you. I didn't understand what 'vacuum freeze' actually does. I
will check the detail
Hi all,
I'm a newbie here. I'm trying to test pgsql with my mysql data. If the
performance is good, I will migrate from mysql to pgsql.
I installed pgsql 9.1rc on my Ubuntu server. I'm trying to import a
large sql file dumped from mysql into pgsql with 'plsql -f'. The file is
around 30G with
well, thank you for the quick reply but actually I'm not concerning the
performance as of now. My problem is related to the bulk insert of
client side program psql. Or, it's a problem of migrating vast data from
mysql to pgsql.
于2011年8月29日 21:25:29,Julio Leyva写到:
check this out
yes, the size of my database(around 200g) is very close to yours. How
long did it take you to migrate the data(100-200G)? I thought about to
write java code to transfer the data but it's a bit trivial. It would be
the best if I can complete this with regular export/import way. if that
won't
Hi Kevin,
Thank you very much for the quick and detailed answers/suggestions. I
will check and try them.
于 2011/8/29 23:18, Kevin Grittner 写道:
Good (but don't forget to change that once the bulk load is done). You
should probably also turn off full_page_writes and synchronous_commit.
I've
Thank you. I didn't understand what 'vacuum freeze' actually does. I
will check the detail to see if it's good for my situation. and I will
also test the load by tcp connection. Thanks again for all your advices
and they are really very helpful to me!
于 2011/8/30 0:06, Kevin Grittner 写道:
Yes, seems so. I separated one of the tables having the problem and did
a test. First, loaded it with original file and saw the same: invalid
command then follows out of memory. After I fixed those escape
characters, the table could be loaded successfully.
于 2011/8/30 10:14, Scott Marlowe 写道:
65 matches
Mail list logo
