n 'host=127.0.0.1 port=5432 client_encoding=C' publication pub1;
오류: 발행 서버에 연결 할 수 없음: 서버에 연결할 수 없음: 연결이 거부됨
"127.0.0.1" 호스트에 서버가 가동 중인지,
5432 포트로 TCP/IP 연결이 가능한지 살펴보십시오.
2017년 08월 23일 22:40에 Peter Eisentraut 이(가) 쓴 글:
On 8/22/17 01:19, Ioseph Kim wrote:
2017-08-22
Hi,
I tried ver. 10 beta3.
I had below messages.
-
$ pg_ctl start
서버를 시작하기 위해 기다리는 중완료
서버 시작됨
2017-08-22 14:06:21.248 KST [32765] 로그: IPv6, 주소: "::1", 포트 5433
번으로 접속을 허용합니다
2017-08-22 14:06:21.248 KST [32765] 로그: IPv4, 주소: "127.0.0.1", 포트
5433 번으로 접속을 허용합니다
2017-08-22 14:06:21.364 KST
Hi,
I propose to append an error message when index name and table name are
same.
example:
postgres@postgres=# create table t (a int not null, constraint t primary
key (a));
ERROR: relation "t" already exists
End users will confusing pretty, because if users meet this message,
users w
Thanks, I agree that strftime() is better then asctime().
regards, Ioseph
2016년 06월 16일 08:37에 Tom Lane 이(가) 쓴 글:
> Alvaro Herrera writes:
>> +1 to strftime("%c"). If we wanted to provide additional flexibility we
>> could have a \pset option to change the strftime format string to
>> something
2016년 06월 15일 01:56에 Tom Lane 이(가) 쓴 글:
I take it from the vast silence that nobody particularly cares one way
or the other. On reflection I think that this would be a good change
to make, so I'll go do so unless I hear complaints soon. regards, tom
lane
I propose to change from asctime()
Hello.
In po.ko (korean message) at psql
#: command.c:2971
#, c-format
msgid "Watch every %lds\t%s"
msgstr "%ld초 간격으로 지켜보기\t%s"
this message string is a cut string, because buffer size is small.
At line 2946 in src/bin/psql/command.c
chartitle[50];
size of message string for korean
"a" is of type boolean but expression is of type
integer(input value = 24) at character 25"
Best regards, Ioseph.
2016-03-15 (화), 13:54 +0800, Craig Ringer:
> On 15 March 2016 at 10:52, Ioseph Kim wrote:
> Hi, hackers.
>
> I had a error message
ds, Ioseph.
2016-03-14 (월), 23:06 -0400, Tom Lane:
> Ioseph Kim writes:
> > I want see that value of bind variable at a server log.
>
> That's available if you turn on log_statements, IIRC.
>
> regards, tom lane
>
>
--
Sent via
debuged to client only.
So, I propose that error value of bind variable will be displayed at a
server log.
in parse_target.c:529,
input parameter value of that node not containded value of column at
client.
I want more detail error log.
Regards, Ioseph Kim
--
Sent via pgsql-hackers mailing list
Thanks.
Korean Document is translating currently.
When that be done, I will announce to official site.
current, translation progress is 50%.
This work is dependent only voluntary support by 6 peoples.
so, translating is very slow. :)
I also hope that many Korean documents appear on the official s
Thanks too!
Korean User Group has been translating PGDoc since 2013.
I'll append Copyright in PGDoc.kr too.
http://postgresql.kr/docs/current/
Regards, Ioseph.
2016-03-04 (금), 17:55 -0800, Joshua D. Drake:
> On 03/04/2016 05:39 PM, Tatsuo Ishii wrote:
> > JPUG (Japan PostgreSQL Users Group) w
On 수, 2016-02-17 at 12:14 +0300, Alexander Lakhin wrote:
> 17.02.2016 09:17, Tatsuo Ishii wrote:
> >> Hi.
> >>
> >> In DocBook 4.2 sgml dtd, figure tag is supported already.
> >> that was implemented for multi output format.
> > Ok, there's no technical problems with figures then. MySQL docs has
Hi.
In DocBook 4.2 sgml dtd, figure tag is supported already.
that was implemented for multi output format.
I remember that very old postgresql document has some picture (eg.
system architecture, ERD ...).
when release new version, these might be changed, nevertheless these can
not been.
this p
Sorry ^^
2016-01-18 (월), 16:10 +0900, Michael Paquier:
> On Mon, Jan 18, 2016 at 3:29 PM, Ioseph Kim wrote:
> > What can I do for next step?
>
> (pgsql-hackers is not the right place to ask that, it is a mailing
> list dedicated to the development and discussion of new feature
Hello,
I want to speak a proposal on PGCon 2016.
Currently I wrote only title of contents.
Main title is "PostgreSQL in Korea".
That proposal contains
* Short history of PostgreSQL in Korea (status of korean user group
and theses works)
* kt (korea telecom) report (for PostgreS
Hello,
at PostgreSQL version 9.5rc1,
at line 934 in pg_recvlogical.c
set_pglocale_pgservice(argv[0],PG_TEXTDOMAIN("pg_recvlogical"));
this references invalid catalog file, because pg_basebackup,
pg_recvlogical, pg_receivexlog commands use same catalog file
pg_basebackup.mo
pg_receivexl
Sorry, i can't receive mailing :(
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi, I'm Korean.
CP51949 is EUC-KR correct.
so, that defined code is correct too.
But in Korea, EUC-KR code is not good to use all Korean character.
In recent years, many people in Korea use the CP949 code.
MS Windows codepage also is CP949.
- Original Message -
From: "Takahiro Itagaki"
At Korea, Johab code is very old encondig.
by the way, cp949 code page is really used in most environments.
Personally speaking, Johab server code set is not need.
I think that PostgreSQL supports UHC (cp949) server code set.
This feature will be greet many Korean. :)
Unfortunately, UHC code set
I misunderstood. :)
path '((0,0),(1,0))' is 'closed' path.
in this case, it's maybe operator calculated return length too.
- Original Message -
From: "Ioseph Kim" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 03, 2007 6:00 AM
Subject: Re
when @-@ operator used at path type,
below query maybe returns 1.
because this path is just line.
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Ioseph Kim" <[EMAIL PROTECTED]>
Cc:
Sent: Saturday, February 03, 2007 5:36 AM
Subject: Re
=> select @-@ lseg '((0,0),(1,0))';
?column?
--
1
(1 row)
=> select @-@ path '((0,0),(1,0))';
?column?
--
2
(1 row)
--
It's maybe bug in v8.2.1
---(end of broadcast)---
TIP 4: Have you searched our list arc
22 matches
Mail list logo
