[BUGS] BUG #2155: problem with UNICODE and KOI8
The following bug has been logged online:
Bug reference: 2155
Logged by: Vic
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.5
Operating system: FreeBSD 6.0
Description:problem with UNICODE and KOI8
Details:
Database have enconding UNICODE.
Client have KOI8,
"lower" function not convert to lower case any russian worlds, but english
words convertable:
acct=> \encoding KOI8
acct=> select lower('ÐÑовеÑка');
lower
--
ÐÑовеÑка
(1 запиÑÑ)
acct=> select lower('Test');
lower
---
test
(1 запиÑÑ)
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
[BUGS] BUG #2172: Problem with query in order by
The following bug has been logged online: Bug reference: 2172 Logged by: Vic Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.6 Operating system: FreeBSD 5.4/6.0 Description:Problem with query in order by Details: when I send query "select * from nets a,systbl where a.type = systbl.tbl_ and a.cid_ = 155 and systbl.tblid = 'nettype' order by a.endd, net; " - all working fine, but when I write in "order by" next: "order by nets.endd,net" (I'm chane a. to nets. ) postgres returrn me linked "a" table with "systbl" by where phrase, and also full link with nets table again Sorry for my bad english :(, I can send to email full describe tables and result of to select ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[BUGS] BUG #6392: leak memory while restore/load dump
The following bug has been logged on the website: Bug reference: 6392 Logged by: Vic Email address: v...@nix.kh.ua PostgreSQL version: 9.0.6 Operating system: FreeBSD/Linux Description: While trying load database dump, postgresql (server process) eat up all memory, including swap. This problem start after update on 9.0.6 and same problem with 9.1.2. PostgreSQL version 9.0.5 load same dump without problem. In syslog on FreeBSD: Jan 11 01:27:48 saturn kernel: swap_pager: out of swap space Jan 11 01:27:49 saturn kernel: swap_pager_getswapspace(16): failed Jan 11 01:27:49 saturn kernel: pid 2020 (postgres), uid 70, was killed: out of swap space Jan 11 01:27:49 saturn kernel: swap_pager: out of swap space Jan 11 01:27:49 saturn kernel: swap_pager_getswapspace(16): failed Jan 11 01:27:50 saturn postgres[2012]: [10-1] WARNING: terminating connection because of crash of another server process Jan 11 01:27:50 saturn postgres[2012]: [10-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. Jan 11 01:27:50 saturn postgres[2012]: [10-3] HINT: In a moment you should be able to reconnect to the database and repeat your command. Jan 11 01:27:50 saturn postgres[2036]: [10-1] WARNING: terminating connection because of crash of another server process Jan 11 01:27:50 saturn postgres[2036]: [10-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. Jan 11 01:27:50 saturn postgres[2036]: [10-3] HINT: In a moment you should be able to reconnect to the database and repeat your command. Notes: dump size in plain format about 650Mb, in c format about 125Mb; database has plpython and postgis. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6392: leak memory while restore/load dump
yes, you right about inet. Thanks for reply! On Wed, 11 Jan 2012, Heikki Linnakangas wrote: On 11.01.2012 02:24, v...@nix.kh.ua wrote: The following bug has been logged on the website: Bug reference: 6392 Logged by: Vic Email address: v...@nix.kh.ua PostgreSQL version: 9.0.6 Operating system: FreeBSD/Linux Description: While trying load database dump, postgresql (server process) eat up all memory, including swap. This problem start after update on 9.0.6 and same problem with 9.1.2. PostgreSQL version 9.0.5 load same dump without problem. You probably have an inet field in the database. 9.0.6/9.1.2 contained a bug causing a memory leak in inet/cidr functions. See: http: //archives.postgresql.org/pgsql-committers/2011-12/msg00086.php http: //archives.postgresql.org/pgsql-bugs/2011-12/msg00068.php This will be fixed in 9.0.7/9.1.3. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Question regarding 'not in' and subselects
Hi. I'm using PostgreSQL 7.4.2 under Fedora Core 1.
I have two tables with a single varchar(32) column in each. I'm trying
to find all the rows from one table that don't exist in the other
table. The query that I am using is:
select u.user_name from users u where u.user_name not in (select
user_name from iasusers);
(Actually, I'm doing something a bit more complex but this illustrates
the problem.)
It always seems to return 0 rows. As a test, I inserted a row into
users that I knew wasn't in iasuses but it didn't make a difference.
If I remove the 'not', the query returns the rows that exist in both
tables.
If I replace the subselect with a list, it seems to work the way that
I'd expect, i.e. "not in ('vic', 'joe')" it shows all the rows from
users except for vic and joe.
Am I doing something wrong or is this a bug?
Thanks,
-Vic
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
Re: [BUGS] Question regarding 'not in' and subselects
On Wed, 2004-05-26 at 14:38, Bruno Wolff III wrote: > On Wed, May 26, 2004 at 13:57:37 -0400, > Vic Ricker <[EMAIL PROTECTED]> wrote: > > Am I doing something wrong or is this a bug? > > Are there any nulls in iasusers.user_name? There was a null in iasusers. I removed it and that fixed the problem. I'm not sure that I understand why. It doesn't seem very intuitive... :-) Tom Innes's suggestion of: select u.user_name from users u where u.user_name not in (select user_name from iasusers ia where ia.user_name = u.user_name); also worked. Thanks guys! -- Vic Ricker http://www.ricker.us/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
