head of the given
offset..."
and:
"Another issue to keep in mind is that in POSIX time zone names,
positive offsets are used for locations west of Greenwich. Everywhere
else, PostgreSQL follows the ISO-8601 convention that positive timezone
offsets are east of Greenwich. ...&q
Tom Lane написа:
"Milen A. Radev" writes:
I reproduced it on Windows Vista 64-bit SP2 with version 8.4.2
[...]
1. Maybe it's specific to Vista and/or Win64?
[...]
Also reproduced it on 32-bit Vista SP2 (with Postgres 8.4.2).
Couldn't reproduced it on neither Win
WildWezyr написа:
On Jan 21, 6:17 pm, mi...@radev.net ("Milen A. Radev") wrote:
[...]
For the test I changed all regional settings to "Polish (Poland)",
restarted the machine, created a new cluster and a new database (using
the commands from the last mail from Heikki).
Tom Lane написа:
"Milen A. Radev" writes:
I reproduced it on Windows Vista 64-bit SP2 with version 8.4.2
(installed by using the One-click installer from EnterpriseDB):
OK, so that means WildWezyr isn't just seeing things. Possibilities
that occur to me now:
1. Maybe it'
ICE: i = 642500
ERROR: duplicate key value violates unique constraint "spb_word_word_key"
CONTEXT: SQL statement "insert into spb_word (word) values ( $1 )"
PL/pgSQL function "spb_runmesimple2" line 15 at SQL statement
--
Milen A. Radev
--
Sent via pgsq
Bruce Momjian написа:
Milen A. Radev wrote:
Tom Lane ??:
"Dmitry Ryabov" writes:
Description:Incorrect log_line_prefix default value in
postgresql.conf
log_line_prefix = '%%t '
(must be log_line_prefix = '%t ')
Uh, the default setting is an empty
rror? If it isn't, perhaps it is a problem in some
packaging of Postgres, but you did not say which package you are
using.
The line looks like that after using the One-click installer
available here - http://www.enterprisedb.com/products/pgdownload.do.
Probably should be sorted out by
AIL: The server's LC_CTYPE setting requires encoding...
>
> Any hint?
Known restriction: "Any character set encoding specified for the new
database must be compatible with the server's LC_CTYPE locale setting."
(http://www.postgresql.org/docs/current/static/s
://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS,
(especially the last paragraph of 4.1.1.),
--
Milen A. Radev
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
The following bug has been logged online:
Bug reference: 3854
Logged by: Milen A. Radev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: Debian Etch
Description:pg_dump dumps renamed primary key constraints by their
old name
Details
re the name of the column.
Could you send the real statement _and_ the error message you've got.
--
Milen A. Radev
---(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
karol dzięgielewski написа:
> Hi,
> Where can I find documentation in pdf format?
> Regards Karol Dzięgielewski
That's not a bug.
http://www.postgresql.org/docs/manuals/
--
Milen A. Radev
---(end of broadcast)---
TIP 4: Have yo
that the psql command window prompts for the password. Have you
> got any idea how to suppress it?
1.http://www.postgresql.org/docs/current/static/libpq-pgpass.html
2.http://www.postgresql.org/docs/current/static/auth-methods.html#AUTH-TRUST
--
Milen A. Radev
:8.2 FOR DEBIAN !!! pl ^^
> Details:
>
> Whats up with the new versions for postgres
Also look here - http://www.backports.org/.
--
Milen A. Radev
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please sen
the table. For backwards compatibility, GRANT/REVOKE RULE is still
accepted, but it does nothing. "
--
Milen A. Radev
---(end of broadcast)---
TIP 6: explain analyze is your friend
On 10/10/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> On 10/10/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> I couldn't duplicate any such leak using your test program here.
> The client and the server were o
On 10/10/06, Tom Lane <[EMAIL PROTECTED]> wrote:
"Milen A. Radev" <[EMAIL PROTECTED]> writes:
> The same test programme has grown (after ~1 million iterations) from 2KB to
> around 40MB used physical memory (as reported by "top").
I couldn't duplicate
The following bug has been logged online:
Bug reference: 2684
Logged by: Milen A. Radev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Debian 3.1
Description:Memory leak in libpq
Details:
Source:
#include
#include
int main(int
't reproduce it with 8.1.2 on Slackware Linux 9.1 (kernel 2.6.15).
By the way I have the crash report files Windows created -
postgres.exe.hdmp, postgres.exe.mdmp, appcompat.txt and manifest.txt.
--
Milen A. Radev
---(end of broadcast)
The following bug has been logged online:
Bug reference: 1505
Logged by: Milen A. Radev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Debian GNU/Linux 3.0
Description:[enhancement] Better link styles for the included
documentation
20 matches
Mail list logo
