Re: [SQL] lower and unicode

Hi, I am using --no-locale by init db. I readet that if I am using some locale the pg will work very slow. Have you noticed some speed penalty by using cs_CZ.utf8. regards, ivan. Miroslav Šulc wrote: pginfo wrote: Hi, I am uusing pg 8.0.1 on FreeBSD 5.3 but I am ready t use the version taht

Re: [SQL] lower and unicode

, UNICODE (UTF8) is not supported because Windows natively supports only UTF16 (I'm just repeating something I have read somewhere). Miroslav pginfo wrote: Hi , I tested the lower with unicode on 8.0.1 and find it not to work. If I have only latin symbols it is working well, but if I try to use

[SQL] lower and unicode

Hi , I tested the lower with unicode on 8.0.1 and find it not to work. If I have only latin symbols it is working well, but if I try to use also cyrillic the lower simpli ignore this symbols and all stay as is. I readet that this will work on 8.x . Exists some one using lower/upper + unicode and w

Re: [SQL] pg primary key bug?

Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: I will to ask if it will be possible to start some querys (I do not know the query) exactly before running vacuum full and to save the results in some log file. If it is possible, we will be able to post the results t

Re: [SQL] pg primary key bug?

Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: You idea was that we have "vacuum full" + update or select for update in the same time. I think it is not the case, because we start vacuum full at 1:00 AM and no one is working in this time.

Re: [SQL] pg primary key bug?

Ragnar Hafstað wrote: On Tue, 2005-02-22 at 10:33 +0100, pginfo wrote: We are using jdbc (jdbc driver from pg) + jboss (java based application server) + connection pool (biult in jboss). ... Will vacuum full generate this problem if we have locked table in this time? (It is

Re: [SQL] pg primary key bug?

Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: In this table we store the last value for the ID of part from other tables. For each table we have one constant in this table. We are using the table as sequence. For Example if we nee to insert the next record in some ta

Re: [SQL] pg primary key bug?

Hi Tom, Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: sorry, but we have the case number 3 in with the same problem. Also this time we do not find any linux box crash nor pg stop or restart. Hmm, well there's *something* mighty curious about the hist

Re: [SQL] pg primary key bug?

stants_str_pkey" primary key, btree (constname, fid) Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: Will upgrade to 8.0 solve this type of problems ? The problem is probably not Postgres' fault at all. I'm wondering about disks with write cacheing ena

Re: [SQL] pg primary key bug?

t  solve the problem. I sendet the log only to show that we do not have any server crash nor pg restart. regards, ivan. regards Iain - Original Message - From: pginfo To: Tom Lane Cc: [EMAIL PROTECTED] ; Michael Glaesemann

Re: [SQL] pg primary key bug?

Hi, Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: Will upgrade to 8.0 solve this type of problems ? The problem is probably not Postgres' fault at all. I'm wondering about disks with write cacheing enabled. And you didn't turn off fsync, I t

Re: [SQL] pg primary key bug?

Hi, Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: Tom Lane wrote: Could we see the system columns on these rows? 01=# select oid,xmin,cmin,xmax,cmax,ctid,* from a_constants_str where constname='DOCPLAID'; oid |

Re: [SQL] pg primary key bug?

Hi, Tom Lane wrote: pginfo <[EMAIL PROTECTED]> writes: 01=# select * from a_constants_str where constname='DOCPLAID' ; constname | fid | constvalue ---+-+ DOCPLAID | 0 | SOF_19738 DOCPLAID | 0 | SOF_19738 (2 rows)

Re: [SQL] pg primary key bug?

AID  |   0 | SOF_19738  a_constants_str | DOCPLAID  |   0 | SOF_19738 (2 rows) regards, ivan. Michael Fuhr wrote: On Thu, Feb 17, 2005 at 04:12:38PM +0100, pginfo wrote: 01=# select * from a_constants_str where constname='DOCPLAID' ; constnam

Re: [SQL] pg primary key bug?

Michael Glaesemann <[EMAIL PROTECTED]To: pginfo <[EMAIL PROTECTED]> >

Re: [SQL] pg primary key bug?

u constnames for the restore). regards, ivan. Michael Glaesemann wrote: On Feb 3, 2005, at 21:53, pginfo wrote: I am using pg 7.4.5 on RedHat AS 3.0. sklad21=# \d a_constants_str Table "public.a_constants_str" Column |

[SQL] pg primary key bug?

Hi , I am using pg 7.4.5 on RedHat AS 3.0. I am using it via jdbc and jboss. I have found big problem about the way pg supports primary keys. The bug was reported from my customers ( we are installed pg with our ERP on ~ 500 costomers) and I do not know hot it is happen. sklad21=# \d a_constants_

Re: [SQL] JDBC Batch Updates

Hi, I think yes. I am running 7.4.1 and also using batchUpdate. I am using this from http://jdbc.postgresql.org/download.html. regards, ivan. beyaRecords - The home Urban music wrote: > Hi, > does anybody know whether the latest JDBC driver for postgreSQL 7.4.1 > supports batch updates? > > tha

Re: [SQL] Interest IN problem on 7.4

Hi, thanks a lot. All is ok now. regards, ivan. Stephan Szabo wrote: > On Sat, 13 Dec 2003, pginfo wrote: > > > Hi, > > > > I am using pg 7.4. > > > > Pls, see this test: > > > > tt07=# update a_cars set dog_or_free=0 where virtualen

[SQL] Interest IN problem on 7.4

Hi, I am using pg 7.4. Pls, see this test: tt07=# update a_cars set dog_or_free=0 where virtualen=0 and dog_or_free=4 and ids NOT IN ( select oc.ids_car_real from a_oferti_cars oc,a_oferti o where oc.IDS_oferti=o.ids and o.date_valid>=9964) AND IDS = 'SOF_9989'; UPDATE 0 tt07=# update a_cars

Re: [SQL] Interest query plan

I have also another good example for a slow left join work. Can I do it better? explain analyze select * from a_doc D join A_SKLAD S ON(D.IDS=S.IDS_DOC) join A_MED M ON(S.IDS_MED=M.IDS) where d .date_op >= 9600 and d.date_op <= 9700; QUER

Re: [SQL] Interest query plan

explain analyze select * from a_doc D left outer join A_SKLAD S ON(D.IDS=S.IDS_DOC) left join A_MED M ON(S.IDS_MED=M.IDS) where d.IDS='SOF_700060'; QUERY PLAN --

[SQL] Interest query plan

Hi all, I am running pg 7.3.1. My query is very simple but pg generates not the best possible plan for me: analyze select * from a_doc D left outer join (A_SKLAD S join A_MED M ON(S.IDS_MED=M.IDS) )on( d.IDS=s.IDS_DOC) where d.IDS='SOF_700060'; The plan is: -

Re: [SQL] SQL Syntax problem

Hi Doris, In oracle (+) is left outer join or right outer join . You need to write: select... fromauswahlkatalog k, beteiligter b left outer join anspruchkorrektur a on(b.bet_id = a.bet_idemp) left outer join v_betkorr f on (a.ask_id = f.ask_id) where k.awk_id = a.awk

Re: [SQL] update and IN vs. EXISTS

Bruno Wolff III wrote: > On Sat, Feb 01, 2003 at 12:40:00 +0100, > pginfo <[EMAIL PROTECTED]> wrote: > > > > If I try to execute: > >update Table1 set fieldForUpdate = 1 where ID IN (select T2.ID from > > Table2); > > it is running very slow

[SQL] update and IN vs. EXISTS

Hi, I have 2 tables Table1 and Table2. The PK for Table1 is declared as name. Table 2 have only 1 field and it is also name ( it is indexed). I will to update all Table1.filedForUpdate for all rows that exists in Table2. In Table1 I have ~ 120 000 rows and in Table2 I have ~ 100 000. If I execu

[SQL] Deleting in order from a table

Hi , I think the question is stupied, but it is importand for me. I have a table tableA ( ,order_num int). I will to delete some records from tableA but in asc or desc order_num-order. Is it possible to write delete from tableA where (some conditions) order by order_num ? Many thanks, ivan

Re: [SQL] Chaning locale sorting order for statements

I am not sure about comparation performance. I have big problems with sort performance in pg by comparing varchar. Also I am not sure if it is possible to get this new funktion to replace the standart sort. regards, Ivan. Tomasz Myrta wrote: > Uz.ytkownik Albrecht Berger napisa?: > > In Oracle I