Re: [BUGS] psql: set \encoding according to the current locale
Am Sonntag, 31. Oktober 2004 22:59 schrieb Martin Pitt: > Currently (i. e. in 7.4.6) psql seems to use the default database > encoding as locale for both its own messages and for database output > strings. Whereas it is only an inconvenience for the latter, psql's > own messages should really respect LANG/LC_MESSAGES environment > variables instead of the database encoding. That's what it does. > It would also be nice to call "set \encoding" to match the locale psql > was called under, at least when it is called interactively. There is no portable interface to match locale encodings to PostgreSQL's encoding names. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG #1303: backend crashes due wrong TCP packet
The following bug has been logged online: Bug reference: 1303 Logged by: Yevgeniy Kondratiev Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.5 Operating system: RHEL3 Description:backend crashes due wrong TCP packet Details: over, i think, network problems or ODBC errors there are some wrong packets which crash postgresql backend. TCP package with postgresql data (hex) 58 00 00 00 00 00 doest it. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #1302: Vacuumdb and vacuumlo should disable statement_timeout
Alex Koh wrote: > I agree with the suggestions to attach it to userids. However, setting the > statement_timeout in the conf file is good as it will enforce everyone to > have some timeout. This will be especially useful in web applications. > > Anyway, I will use ALTER USER to do it and disable statement_timeout in the > conf file. Yep, that's how I would do it. If you want it on in the config file you should turn it off for super-users. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] [pgsql-bugs] Daily digest v1.1281 (14 messages)
Michael, Ralph, etc.:
> Rules are macros, so when you refer to NEW.storage_id in the rule
> then the default expression "nextval('tmp_storage_id_seq')" is
> evaluated again. ÂIf you don't want that to happen then use a
> trigger.
>
> This comes up often -- maybe somebody could add it to the FAQ.
The reason it comes up often is that the "log" example is in our docs. Since
it doesn't work as expected, I think we need to patch the docs.
H ... would it be possible for the rule to call currval() instead of
NEW.id?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
[BUGS] BUG #1304: update does not honor order of subselect
The following bug has been logged online:
Bug reference: 1304
Logged by: Brendan Fagan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.6
Operating system: RedHat ES 3
Description:update does not honor order of subselect
Details:
SQL Update command does not follow the order of a WHERE field IN subselect.
In the following code, I try to reset the order of rows in a column by
updating an order field. Update does not honor the order of output form the
subselect.
create temp sequence foo increment 1 minvalue 0 start 0;
select setval('foo', 0);
update nav_content_structure
set nav_cannister_ord_num = nextval('foo')
where nav_content_id in (
select s.nav_content_id
fromnav_content_structure s,
nav_content c
where s.nav_content_tie_id = 2624
and s.nav_cannister_id is not null
and c.nav_content_id = s.nav_content_id
order by s.nav_cannister_id, c.nav_content_title )
and nav_content_tie_id = 2624
---(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
