On Fri, Aug 06, 2010 at 01:35:58PM +0900, 노현석 wrote:
> hi..
>
> when using oracle sqlplus.. we can specify password.
> $ sqlplus system/manager
>
> Could you teach me, How can we specify password when using psql
> $ psql -p 5432 -h rac2 -d mydb -U hsnoh
> Password for user hsnoh:
>
> Th
hi..
when using oracle sqlplus.. we can specify password.
$ sqlplus system/manager
Could you teach me, How can we specify password when using psql
$ psql -p 5432 -h rac2 -d mydb -U hsnoh
Password for user hsnoh:
Thanks..
noh019님의 블로그
안녕하세요.
2010/8/6 Devrim GÜNDÜZ :
> Why can't I see psql there? Is it just because that logging is performed
> just before detecting application name?
Yes. The backend checks whether target database exists, before
processing application name.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPOR
I have a table of around 200 million rows, occupying around 50G of disk. It
is slow to write, so I would like to partition it better.
The table is roughly:
id: integer # unique from sequence
external_id : varchar(255) # unique, used to interface with external
systems, not updated (only selec
I am logging application name in 9.0, and noticed the following issue.
First, I produced an error with psql:
bash-3.2$ psql nonexistent
psql: FATAL: database "nonexistent" does not exist
Looking at the logs, I see:
10338 [unknown] 2010-08-06 07:38:00 EEST FATAL: database "nonexistent"
does no
2010/8/6 Rikard Bosnjakovic :
> On Fri, Aug 6, 2010 at 04:41, John Gage wrote:
>
> [...]
>> So, perhaps what is needed in any sort of battle with MySQL is an
>> introductory documentation that gives specific examples of how to achieve
>> "oh wow!" worthwhile results quickly with Postgres.
>
> Bruc
On Fri, Aug 6, 2010 at 04:41, John Gage wrote:
[...]
> So, perhaps what is needed in any sort of battle with MySQL is an
> introductory documentation that gives specific examples of how to achieve
> "oh wow!" worthwhile results quickly with Postgres.
Bruce Momjian's book is an excellent primer:
Postgres has a very gentle learning curve. By which I mean that it
takes an extremely long time, perhaps a lifetime, to fully appreciate
it. On the other hand, it is definitely worth it. Each new discovery
is worth the effort and the wait.
But most people, including myself, don't even wa
Skills Needed:
SQL language knowledge: SELECT, JOINS, TRIGGERS, STORED PROCEDURES,
FUNCTIONS.
Can figure out how to do the above in our 3 database engines:
(PostGre, MySQL, MS SQL)
Front-end knowledge: JavaScript, CSS, HTML
Any web language that is object oriented knowledge: PHP, Ruby, Pearl,
Java,
Gordon Shannon writes:
> Hi, Running 8.4.4 on Centos. A couple of these numbers don't make sense to
> me.
> (I added line numbers for reference)
> 11 INFO: "authors_archive": found 16558 removable, 7300 nonremovable row
> versions in 492 out of 51958 pages
The key point here is that vacuum on
"Edmundo Robles L." writes:
> i have the above error when i tried to insert a register, How can i
> solve this issue???'
AFAIK the only way to get that message is for one session to be starting
to do something with a table just at the time that some other session
drops it. Maybe you need to
Hi !
i have the above error when i tried to insert a register, How can i
solve this issue???'
regards .
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi, Running 8.4.4 on Centos. A couple of these numbers don't make sense to
me.
(I added line numbers for reference)
1 vacuum verbose authors_archive;
2 INFO: vacuuming "public.authors_archive"
3 INFO: scanned index "authors_archive_pkey" to remove 45878 row versions
4 DETAIL: CPU 0.05s/0
Richard wrote:
pg_start_backup is rather slow, can I change checkpoint to
CHECKPOINT_IMMEDIATE?
Starting in PostgreSQL 8.4, pg_start_backup takes an optional second
parameter that asks it to do an immediate checkpoint if you set it
true: http://www.postgresql.org/docs/8.4/interactive/fu
Please post in plain text if possible.
2010/8/5 노현석
>
> hi..
>
> we test locking PostgreSQL 8.4.4 on x86_64.
> $
> $ kill -9 5143
What you want is plain old
kill 5143
or
kill -SIGTERM 5143
Kill -SIGTERM is like using a fly swatter to kill a fly. SIGKILL (-9)
is like lobbing a grena
Hi,
On Thu, 05 Aug 2010 17:52:44 +0900 노현석 wrote:
> we test locking PostgreSQL 8.4.4 on x86_64.
>
[...]
> begin;
> delete from citytest;
> <--- no commit/rollback
> <--- this will be Blocker
>
> 2> session 2,3,4
> ###
> $ psql mydb
> delete from citytest;
http://groups.yahoo.com/group/syrilalwinl/message
n Bayern 646
Ludwig III. von Bayern: Gesuch Hitlers an L. 179
Lueger, Dr. Karl, BegrunderderChristlich-sozialen Partei (s. diese): L. und die
Christlich-soziale Partei
2010/8/5 노현석
> Could you teach me,Is this expected behavior ?? (disapper blocking
> process not only Blocker process)
> and
> Could you teach me, how can we eliminate just Blocker session...
>
> instead of going to the OS to kill the process, just type ctrl-c into the
psql terminal ses
On 02/08/2010 21:14, John R Pierce wrote:
Another factor, if your linux system was using LVM (its the default
storage configuration on many distributions), there's a pretty good
chance the drive mapper is ignoring write barriers, which greatly speeds
up random writes at the expense of reliable co
On Thu, Aug 5, 2010 at 9:40 AM, Szymon Guz wrote:
> killing it with -9 crashed the whole PostgreSQL server, don't do that.
> Instead just login to the database and run the function
> pg_cancel_backend() http://www.postgresql.org/docs/8.4/static/functions-admin.html,
> much more safe way.
Or, assu
pg_start_backup is rather slow, can I change checkpoint to
CHECKPOINT_IMMEDIATE?
--
Richard
2010-08-05
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgs
=?EUC-KR?B?s+vH9ryu?= writes:
> $ kill -9 5143
[ and all the other backends disappear too ]
> Could you teach me, Is this expected behavior ?
Yes. That is not the recommended way to kill a backend.
Try pg_terminate_backend().
regards, tom lane
--
Sent via pgsql-gener
Le 05/08/2010 10:52, 노현석 a écrit :
> [...]
> we test locking PostgreSQL 8.4.4 on x86_64.
>
> 1> session 1
> ###
> $ psql mydb
> drop table citytest;
> CREATE TABLE citytest (
> i_id integer ,
> city varchar(80)
> ) ;
> ALTER TABLE citytest ADD CONSTRAINT citytest_pkey P
In response to ?? :
> so. i killed Session 1's PID with kill -9 commands
What have you killed, the client or the postmaster?
Regards, Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG: 0x31720C99, 1006 CCB4 A326 1D42 6431 2EB0 389D 1DC
In response to ?? :
> today, I found this situation.
>
>
>
> Session 1. -
>
> begin;
> delete from ;
>
>
> Session 2 -
>
> delete from ;
>
>
> thus, it occured row level locking.
>
>
>
>
> so. i killed Session 1's PID with kill -9 commands
>
>
> but. both s
Never kill -9. Use kill -INT, whatever signal num that is, 11?
Sent from my iPhone
On Aug 5, 2010, at 3:14 AM, 백승엽 wrote:
> Hi.
>
>
> I am korean database engineer.
>
> my english skill is very poor.
>
> but i desire that you teach this situation.
>
>
> um...
>
> I am testing pos
2010/8/5 백승엽
> Hi.
>
>
> I am korean database engineer.
>
> my english skill is very poor.
>
> but i desire that you teach this situation.
>
>
> um...
>
> I am testing postgresql performance in these days;
>
> today, I found this situation.
>
>
>
> Session 1. -
>
> begin;
> delete from ;
>
>
Hi.
I am korean database engineer.
my english skill is very poor.
but i desire that you teach this situation.
um...
I am testing postgresql performance in these days;
today, I found this situation.
Session 1. -
begin;
delete from ;
Session 2 -
delete from ;
thus, it occure
hi..
we test locking PostgreSQL 8.4.4 on x86_64.
1> session 1
###
$ psql mydb
drop table citytest;
CREATE TABLE citytest (
i_id integer ,
city varchar(80)
) ;
ALTER TABLE citytest ADD CONSTRAINT citytest_pkey PRIMARY KEY (i_id);
insert into citytest values (1,'aaa');
i
On Thu, Aug 05, 2010 at 06:23:54PM +0600, AI Rumman wrote:
>I need to write a query to find the primary key column_names that depend
>on sequences.
>Any help please.
On the assumption that the sort of dependence you're looking for is one where
a column has a default value of nextval('s
I need to write a query to find the primary key column_names that depend on
sequences.
Any help please.
Hi,
I've got a view, which is supposed to be called with a WHERE clause, like:
SELECT * FROM data_view WHERE od_id = '1234';
I'd like to make sure it is called correctly: not
On 05/08/10 06:03, Nick wrote:
> Anyone? Please
It's probably going to be a lot easier to do this with a stored
procedure. I don't rate your chances of making it work with a rule.
Rules work more like a macro system, and I'm not sure they can be
convinced to do what you're trying to do.
--
Craig
33 matches
Mail list logo
