Tom Lane wrote:
> The reason those aren't getting translated is that the Italian
> translations have not been updated for 8.1 --- the entries in it.po
> still look like the 8.0 wording:
It might be possible with little effort to rework this so that the
prompts display the letters that are actuall
I've reported variants of this in the past, but this case is entirely
repeatable.
Executing this query:
select st_id, min(seed_id) as "initial_seed_id", count(*) as
"seed_count"
from seed group by st_id;
The query plan and table stats are:
QUERY PLAN
"Massimo Fidanza" <[EMAIL PROTECTED]> writes:
> Hi, I discover a very annoying bug in the create user command. I have the
> environment variable LANG=it_IT.UTF-8 and when I try to crate a new user wit
> the create user command, at he prompt I have the three questions
> Shall the new role be a supe
Jeff Davis <[EMAIL PROTECTED]> writes:
> So the postgresql.conf setting "standard_conforming strings" that turns
> off backslash escaping affects the interpretation of other
> postgresql.conf settings?
No, it doesn't. Backslashes are still escapes within postgresql.conf.
On Mon, 2006-09-18 at 13:37 -0400, Bruce Momjian wrote:
> Yes, this is required because we use backslashes for escapes. The
> backslashing can be turned off in 8.2.
>
So the postgresql.conf setting "standard_conforming strings" that turns
off backslash escaping affects the interpretation of othe
Hans Postma wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2634
> Logged by: Hans Postma
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: Windows XP VM virtual server
> Description:path requires double \\ for WA
I'll see what I can get done, I'll need to get it to lockup again as
I've killed everything to try other options. I have a feeling that the
only reason it worked on 8.1.3 before was because it was on slower
servers which were also running other stuff. My new database server is
very fast and only ru
The 8.1.4 shows POSTGIS="1.1.3" GEOS="2.2.1-CAPI-1.0.1" PROJ="Rel.
4.4.7, 31 March 2003" USE_STATS and the 8.1.3 shows POSTGIS="1.1.2"
GEOS="2.2.1-CAPI-1.0.1" PROJ="Rel. 4.4.7, 31 March 2003" USE_STATS
I've been playing with this a bit more by switching to 8.1.3 with
postgis 1.1.3 and still get th
The following bug has been logged online:
Bug reference: 2635
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows
Description:manual service registration after install
Details:
1. Manual create user "postgres" with passwo
The following bug has been logged online:
Bug reference: 2634
Logged by: Hans Postma
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP VM virtual server
Description:path requires double \\ for WAL archiving
Details:
Hi there
Tryin
The following bug has been logged online:
Bug reference: 2632
Logged by: Massimo Fidanza
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Ubuntu 6.04
Description:createuser language poblem
Details:
Hi, I discover a very annoying bug in th
The following bug has been logged online:
Bug reference: 2633
Logged by: Massimo Fidanza
Email address: [EMAIL PROTECTED]
PostgreSQL version: xx
Operating system: xxx
Description:Bug report wizard link broken
Details:
After bug report reporting (the page whe
[EMAIL PROTECTED] napsal(a):
Compiling PostgreSQL 8.1.4 under Solaris 10, I ran into a problem documented
back on 2006-05-30. Apparently in order to compile successfully, one has to
remove an unreferenced function pqsignalinquire() in
src/interfaces/libpq/pqsignal.c.
Since I stepped into th
13 matches
Mail list logo
