The following bug has been logged online:
Bug reference: 4624
Logged by: Alexander
Email address: alscherba...@yandex.ru
PostgreSQL version: 8.3
Operating system: Windows Server 2003
Description:pg_restore
Details:
Добрый день.
такая ситуация:
я восстанавливаю
The following bug has been logged online:
Bug reference: 4712
Logged by: Alexander
Email address: alexan...@energy.at
PostgreSQL version: latest
Operating system: windows xp
Description:Installing problems
Details:
i cant get by the password asked in the installer
The following bug has been logged online:
Bug reference: 5489
Logged by: Alexander
Email address: goa...@gmail.com
PostgreSQL version: 8.3.11
Operating system: CentOS 5.4
Description:SELECT ... RETURNING INTO ... in ecpg
Details:
I've been using PostgreSQL
anyone know, what can be wrong?
--
С уважением,
Alexander mailto:goa...@gmail.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
sfered over the
network).
1 ноября 2011 г. 8:43 пользователь Craig Ringer написал:
> On 01/11/11 02:46, Alexander wrote:
> > Hi all.
> >
> > I've encountered the following problem: pg_restore hangs while
> > restoring LOBs. The situation is as follows
The following bug has been logged online:
Bug reference: 4364
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: FreeBSD 7.0
Description:type of "new.id" does not match that when preparing the
plan
Detail
gt; insert into t1
> select distinct (t1.a + t2.a)*2
> from t1,t2
> where not exists (
> select * from t1 tt where tt.a = (t1.a + t2.a)*2
> )
I assume there is now a hashed ANTI-SEMI-JOIN operator implemented?
Thanks
Alexander
--
Dipl.-Math. Alexander Steffens
Dorotheenstr. 16
2356
1. JDBC Driver returns empty separator in the database catalog.
2. Why JDBC Driver returns column (procedures etc.) name pattern in lower case?
Al
Hi.
I use version from cvs.
I want to have array of referencies to another table, so I do:
cms=# create table a (a int primary key); create table b (b int[]
references a);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
table 'a'
CREATE
NOTICE: CREATE TABLE will create
Hi.
I using version from CVS, and after update tried to run `make
distclean'. For some reason my GNUMakefile was deleted, so Makefile is
used by gmake and I got an error message (see Subj)
The reason is
@if ! [ -f GNUmakefile ] ; then \
^^^ in the Makefile
To fix it should b
Hi.
I get psql from CVS and try
configure --with-tcl --with-perl --with-python --with-openssl --with-CXX
&& make
And I got
...
gcc -Wall -Wmissing-prototypes -Wmissing-declarations
-L/usr/local/ssl/lib -Wl,-R/usr/local/pgsql/lib access/SUBSYS.o
bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.
Hi.
uname -a
SunOS iridium 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-5_10
python
Python 2.0b1 (#5, Sep 12 2000, 13:36:09)
[GCC 2.95.2 19991024 (release)] on sunos5
I use cvs version, after update I tried:
make distclean; configure --with-tcl --with-perl --with-python
--with-openssl --with-C
Hi.
I use bleadperl and try to compile plperl with it:
SunOS iridium 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-5_10
gcc version 3.1 20010308 (experimental)
perl5 (revision 5.0 version 7 subversion 0)
pgsql from CVS
configure --prefix=${PREFIX}/pgsql --with-tcl --with-perl --with-python
--with
Hi all.
First time I execute `make check' 10 tests failed:
float8 ... FAILED
test numerology ... FAILED
point... FAILED
lseg ... FAILED
interval ... FAILED
test geometry ... FAILED
test horology
On Thu, 22 Mar 2001, Peter Eisentraut wrote:
> In src/test/regress/pg_regress[.sh], line 163, change
>
> *-*-qnx* | *beos*)
>
> to
>
> *-*-qnx* | *beos* | *solaris*)
>
> and rerun the tests. This will avoid using Unix domain sockets, which are
> broken on Solaris.
Yes, it works now:
On Thu, 22 Mar 2001, Tom Lane wrote:
> What I see is a lot of
>
> ! psql: Backend startup failed
>
> which suggests a fork() failure. Look in the postmaster logfile to see
> the exact kernel error code --- but probably you are out of swap space
> or up against the kernel's limit on number of pr
INSERT INTO "ObjectLog1" VALUES (1, '2001-05-02 13:48:59.999', 0, 10, 1, 1,
9, 0, 0, 0, 0);
djs=# select "Date" from "ObjectLog1";
Date
---
2001-05-02 13:48:60.00+03
(1 row)
--->13:48:60.00 !!
It supposed to be 13:49:00.00
Also this bug l
djs=# SELECT version();
version
---
PostgreSQL 7.1 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)
INSERT INTO "ObjectLog1" VALUES (1, '2001-05-02 13:48:59.999', 0, 10, 1, 1,
9, 0, 0, 0, 0);
djs=# select "Da
Look this:
create table tmp (create_datetimestamp);
#insert into tmp values('2001-04-01 02:29:52');
INSERT 1021715 1
#select * from tmp;
create_data
2035-05-29 01:33:36-05
(1 row)
! ! ! !
It's work on FreeBSD 4.2. PostgreSQL install from:
postgresql-7.1.1.tar
1
Terminating any active server processes...
Server processes were terminated at Tue May 22 16:11:21 2001
Reinitializing shared memory and semaphores
Is this bug or feature?
Alexander Zagrebin
--
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Hi!
> "Alexander Zagrebin" <[EMAIL PROTECTED]> writes:
> > But if "rec" is declared as "hierarchy%ROWTYPE", then
> > execution fails with such log messages:
>
> I can't duplicate this in current sources. Please try 7.1.2.
>
The following bug has been logged online:
Bug reference: 2476
Logged by: Alexander Cordeiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Win XP
Description:Instalation problem
Details:
I'm trying to install PostgreSQL 8.1, fo
The following bug has been logged online:
Bug reference: 2482
Logged by: Alexander Galler
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows XP
Description:Wrong result in timestamp_in, timestamptz_in, date_in
Details:
SET SESSION
The following bug has been logged online:
Bug reference: 2493
Logged by: Alexander Pravdin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows XP
Description:bug with initdb under an administrator
Details:
If I run the initdb under
The following bug has been logged online:
Bug reference: 2531
Logged by: Alexander Dupuy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Fedora Core 5
Description:missing header dependency in src/port/Makefile
Details:
While there is a
ual time=2.758..2.760 rows=1 loops=999)
-> Seq Scan on t1 subselect (cost=0.00..17.49
rows=333 width=0) (actual time=0.055..1.736 rows=499 loops=999)
Filter: (i4 < $0)
Total runtime: 2821.200 ms
Best regards,
Alexander Kirpa
--
The following bug has been logged online:
Bug reference: 3561
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: FreeBSD 6.2
Description:CHAR(x) blank stripped. Server or documentation bug?
Details:
Regarding
The following bug has been logged online:
Bug reference: 3826
Logged by: Alexander Steffens
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3b4
Operating system: Win2003R2x64
Description:Very Slow Execution of examplequery (wrong plan?)
Details:
Hello, I
able to do in about
log(5*10^6)*5*10^6. so there is a gap of nearly factor 1000.
for me it looks like it can not rotate the calculation of the
expression (2*(a1+a2)) outside of the "not exists"?
best regards, alexander.
PS: I will now let the query run to an end if it takes less
The following bug has been logged online:
Bug reference: 4106
Logged by: Alexander Strotmann
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP / Windows 2003 Server
Description:WHERE - clause in view works only sometimes
Details
ienst, telefon_privat, email,
anzahl_tage_erinnerung, gebietsschutz) VALUES (100, 'Alexander',
'Strotmann', 'alex', '534b44a19bf18d20b71ecc4eb77c572f', '1',
'Test', 'Teststraße', '7', '+49 0251/123', NULL, '[
Indeed a simple "delete from alex" demonstrates that this does indeed work. However, it appears that within the function this is not happening or that the insert statements cannot see the full extent of the changes made by the delete statement. Whichever, surely this is wrong?
Regards,
Alexander Stanier.
mailto:[EMAIL PROTECTED]
)
at
org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1St
atement.java:153)
The response type code is random, implying that the client is receiving
unexpected data from the back end.
PostgreSQL 7.3.4, Sun Java2 SDK 1.4.2, Windows (Cygwin).
Alexander
This is normaol behavior.
> I belive that I have found a bug - or maybe it was done on purpose. Have
> a look at this query:
>
>
> SELECT integer_field FROM bugtable WHERE (CASE WHEN '' <> '' THEN
> integer_field = '' ELSE integer_field = 0 END);
> Result: ERROR: invalid input syntax for integer:
Bug in 7.4.2.. Concern with handling of Double Quotation Marks (").
Escape of double quotation marks can't solve the problem.
--
CREATE TABLE public.test
(
my_column varchar NOT NULL,
CONSTRAINT my_primary PRIMARY KEY (my_column)
) WITHOUT OIDS;
---
CREATE TABLE public.ref_tes
POSTGRESQL BUG REPORT TEMPLATE
Your name : Alexander Troppmann
Your email address : [EMAIL PROTECTED
There is bug in 7.4.2, concerning unicode and russian letters. For db
in unicode russian data doesn`t order in alphabetical order (rows group
with the same first letter but not in alphabetical order).
SELECT "person" from my_table ORDER BY "person";
Rows group in such order (approximately): Ð-Ð-
background disk writer and improving using of shared buffers.
Good DB engine have more knowledge about information in
shared buffers and using her, that any disk cache system of OS,
plus avoiding or minimize using cache remove don't need
"moving" between cache and buffers.
Best reg
PostgreSQL 8.0 Beta 2 OS: Windows 2000/XP
Run: pg_dumpall -U dba
Output:
...
ALTER USER dba WITH PASSWORD '111'
CREATEDB CREA
TEUSER;
\connect monk
pg_dump.exe: [archiver (db)] connection to database "monk" failed:
FATAL: user "'dba'" does not exist
pg_dumpall.exe:
false :funcformat 0 :args ({RELABELTYPE :arg {VAR :varno 1 :varattno
2 :vartype 1043 :vartypmod 64 :varlevelsup 0 :varnoold 1 :varoattno 2}
:resulttype 25 :resulttypmod -1 :relabelformat 1})})
Thanks,
Alexander
The following bug has been logged online:
Bug reference: 1395
Logged by: Alexander Rodríguez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 RC5
Operating system: Windows
Description:Connection
Details:
When I add a server in Windows XP with service pack
The following bug has been logged online:
Bug reference: 1396
Logged by: Alexander Rodríguez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 RC5
Operating system: Windows
Description:Connection
Details:
When I add a server in Windows XP with service pack
The following bug has been logged online:
Bug reference: 1427
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: FreeBSD 5.2.1
Description:Seq scan for SELECT 1 FROM p WHERE aid=133 LIMIT 1
Details:
CREATE TABLE
SELECT to_char(NOW() - '2000-10-02'::date, 'MonDD');
Clear CRASH and autorestart.
Need fix :-|
pg 8.0.1 FreeBSD 5.2.1
Core size 3334144
Best regards,
Alexander Kirpa
---(end of broadcast)---
TIP 7: don't forget to
The following bug has been logged online:
Bug reference: 1632
Logged by: Alexander Rusinov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: FreeBSD 5.4-PRERELEASE i386
Description:Several jailed PostgreSQL instances.
Details:
Only one
- Original Message -
From: "Alexander Volk" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 17, 2005 11:15 AM
Subject: Error when install
=== BACKUP YOUR DATA! =
As always, backup your data before
upgrading. If the upgrade le
The following bug has been logged online:
Bug reference: 1900
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1beta2
Operating system: FreeBSD 5.2
Description:pgdumpall: false function description for type 'opaque'
Details
The following bug has been logged online:
Bug reference: 2186
Logged by: Alexander Yeliseyev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: SuSe Linux 9.2
Description:syntax error in postgresql.conf
Details:
[EMAIL PROTECTED
The following bug has been logged online:
Bug reference: 2274
Logged by: Alexander Galler
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows XP
Description:Error in 'CREATE DOMAIN' SQL command in dump file
Details:
I ha
The following bug has been logged online:
Bug reference: 2302
Logged by: Alexander Pivovarov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.1
Description:\d command gets double quoted table name in error
message - ""
The following bug has been logged online:
Bug reference: 2304
Logged by: Alexander Pivovarov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.1
Description:Time zone bug: '05:04 GMT+3' processing as '05:04:
The following bug has been logged online:
Bug reference: 2315
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Crash engine after modify "active" function
Details:
FUNCTION f1(
On 15 Mar 2006, at 19:54, Tom Lane wrote:
> "Alexander Kirpa" <[EMAIL PROTECTED]> writes:
> > Description:Crash engine after modify "active" function
>
> I can't reproduce this in HEAD. I think it's probably the same bug
> already re
The following bug has been logged online:
Bug reference: 2353
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Temporary tables created within trigger function still
exist after abend
The following bug has been logged online:
Bug reference: 2394
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Multiple TRUNCATE within transaction
Details:
Within one transaction each
The following bug has been logged online:
Bug reference: 5643
Logged by: Alexander Pyhalov
Email address: a...@rsu.ru
PostgreSQL version: 8.4.4
Operating system: FreeBSD 8.1
Description:ecpg program doesn't process WHENEVER NOT DATA FOUND
Details:
I have
The following bug has been logged online:
Bug reference: 5714
Logged by: Alexander Loechel
Email address: alexander.loec...@unibw.de
PostgreSQL version: 8.4.5
Operating system: Ubuntu Server 10.04. LTS
Description:TZ pattern error on to_timestamp
Details:
After an
The following bug has been logged online:
Bug reference: 6277
Logged by: Alexander LAW
Email address: exclus...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Windows
Description:Money datatype conversion wrong with Russian locale
Details:
When lc_monetary
processed as specified in lconv. And maybe mon_decimal_point,
currency_symbol and negative_sign should be allowed to be empty too if
it's defined by a locale.
Best regards,
Alexander
29.10.2011 20:17, Tom Lane writes:
"Alexander LAW" writes:
It's caused by wrong mon_thousan
two bytes.
And IMHO the locale sanity check better move to PGLC_localeconv and
don't perform these checks with each number conversion.
Best regards,
Alexander.
30.10.2011 23:09, Tom Lane пишет:
Alexander Lakhin writes:
I think there is no need to leave such assumptions. I would p
The following bug has been logged on the website:
Bug reference: 6347
Logged by: Alexander Fortin
Email address: alexander.for...@gmail.com
PostgreSQL version: 9.1.2
Operating system: Ubuntu 10.04.3
Description:
Hi folks. I'm testing 9.1.2 (source com
pgrade/option.c
log_opts.debug_fd = fopen(DEVTTY, "w");
By the way, is there any reason to use stderr for the prompt output, not
stdout?
Regards,
Alexander
16.03.2012 23:13, Alvaro Herrera пишет:
Excerpts from exclusion's message of sáb mar 03 15:44:37 -0300 2012:
I'm using
Thanks, I've understood your point.
Please look at the patch. It implements the first way and it makes psql
work too.
Regards,
Alexander
20.03.2012 00:05, Alvaro Herrera пишет:
Excerpts from Alexander LAW's message of dom mar 18 06:04:51 -0300 2012:
I see two ways to resolve
the dump encoding and thus
they're getting unreadable when different encoding is used.
The same can be reproduced in Linux (where console encoding is UTF-8)
when doing dump with Windows-1251 or Latin1 (for western european
languages).
Thanks,
Alexander
The following bug has been logg
go through some
conversation function.
I think that the last solution is the solution. What is your opinion?
In fact the problem exists even with a simple installation on Windows
when you use non-English locale.
So the solution would be useful for many of us.
Best regards,
Alexander
P.S. sorr
Hello,
C. We have one logfile with UTF-8.
Pros: Log messages of all our clients can fit in it. We can use any
generic editor/viewer to open it.
Nothing changes for Linux (and other OSes with UTF-8 encoding).
Cons: All the strings written to log file should go through some
conversation function.
myself to work on an automated crash-test system for virtual plug-pull
testing, so I'm not stepping up.
I see you point and I can prepare a prototype if the proposed (c)
solution seems reasonable enough and can be accepted.
Best regards,
Alexander
--
Sent via pgsql-bugs mailing list (pg
The initial issue was that log file contains messages in different
encodings. So transcoding is performed already, but it's not
This is not true. Transcoding happens only when PostgreSQL is built
with --enable-nls option (default is no nls).
I'll restate the initial issue as I see it.
I have Win
And regarding mule internal encoding - reading about Mule
http://www.emacswiki.org/emacs/UnicodeEncoding I found:
/In future (probably Emacs 22), Mule will use an internal encoding
which is a UTF-8 encoding of a superset of Unicode. /
So I still see UTF-8 as a common denominator for all the enco
Ok, maybe the time of real universal encoding has not yet come. Then
we maybe just should add a new parameter "log_encoding" (UTF-8 by
default) to postgresql.conf. And to use this encoding consistently
within logging_collector.
If this encoding is not available then fall back to 7-bit ASCII.
What
Sorry, it was inaccurate phrase. I mean "if the conversion to this
encoding is not avaliable". For example, when we have database in
EUC_JP and log_encoding set to Latin1. I think that we can even fall
back to UTF-8 as we can convert all encodings to it (with some
exceptions that you noticed).
I like Craig's idea of adding the client encoding to the log lines. A
possible problem with that (I'm not an encoding expert) is that a log
line like that will contain data about the database server meta-data
(log time, client encoding, etc) in the database default encoding and
database data (the
cale_pgservice(argv[0], PG_TEXTDOMAIN("postgres"));
in main.c, so it would reflect the same behavior as in
postinit.c/CheckMyDatabase.
I tested the patch on Windows and it works.
Best regards,
Alexander
--- D:\src\main.c 2012-08-13 11:56:48.0 +0400
+++ D:\src\postgresql\src\backe
x27;t. So it seems, there should be conversion from
ConsoleCP() to ACP() and then probably to UTF-8 to make postgres
utilities support national chars in passwords or usernames (with
createuser --interactive).
I think it can be fixed as another bug too.
Best regards,
Alexander
10.10.2012 15:
I need download PostgreSQL 8.0.2 but this link has problem.
http://www.postgresql.org/ftp/binary/v8.0.2/win32/
<http://postgresql.mirrors-r-us.net/ftp/binary/v8.0.2/win32/index.html>
Ing. Alexander Gallardo Torres
Jefe Divisiòn de Sistemas
Tel: (57) (5) 6600671 - 6641515 E
The following bug has been logged online:
Bug reference: 4670
Logged by: Alexander V. Chernikov
Email address: melif...@ipfw.ru
PostgreSQL version: 8.3.3
Operating system: FreeBSD 7.1
Description:Cannot get domain constraint names from psql
Details:
It would be
If a column type is being changed with USING (NULL) clause,
NOT NULL constraint seems not to be checked:
[EMAIL PROTECTED] CREATE table test (x integer not null);
CREATE TABLE
[EMAIL PROTECTED] INSERT INTO test VALUES (1);
INSERT 0 1
[EMAIL PROTECTED] ALTER TABLE test ALTER x TYPE boolean USING (N
(sorry if it's a dup)
In 7.4.3, if I rename a column which references another table,
constraint trigger fails on update or delete from main table.
There are a couple of similar (and about rename table itself) reports
for 7.0, 7.1 (as Tom Lane said, rename table is fixed in 7.2), but I
see no more
In 7.4.3, if I rename a column which references another table,
constraint trigger fails on update or delete from main table.
There are a couple of similar (and about rename table itself) reports
for 7.0, 7.1 (as Tom Lane said, rename table is fixed in 7.2), but I
see no more reports since 2001.
H
Consider the following example for 7.4.3
% cat test.sql
CREATE SCHEMA test_schema;
SET search_path TO test_schema;
CREATE TABLE test_table (
x serial,
s bigint
) WITHOUT OIDS;
CREATE FUNCTION test_update_s() RETURNS trigger AS '
BEGIN
SELECT INTO NEW.s sum(x) F
On Sat, Jul 24, 2004 at 01:56:02AM +0400, Alexander M. Pravking wrote:
> But the following works:
>
> [EMAIL PROTECTED] SET search_path TO test_schema;
> SET
> [EMAIL PROTECTED] INSERT INTO test_table DEFAULT VALUES ;
> INSERT 0 1
> [EMAIL PROTECTED] SET search_path TO p
As been said, in 7.4.5 CIDR data type has been accepted values with
non-zero bits to the right of >24-bit mask:
http://archives.postgresql.org/pgsql-bugs/2004-10/msg00081.php
In CVS head src/backend/utils/adt/network.c (1.54) has a fix by Bruce,
but 7.4.6 still has 1.47.2.1 with no fix.
I wonde
On Fri, Nov 12, 2004 at 11:37:24AM -0500, Bruce Momjian wrote:
> Alexander M. Pravking wrote:
> >
> > As been said, in 7.4.5 CIDR data type has been accepted values with
> > non-zero bits to the right of >24-bit mask:
> >
> > http://archives.postgresql
If I don't specify time zone either in config or using "SET TimeZone"
first, "SET TimeZone" inside a transaction isn't rolled back. System
time zone is actually Europe/Moscow. Here's an example:
[EMAIL PROTECTED] SELECT current_setting('TimeZone'), now();
current_setting | now
--
Docs say: Only the database owner or a superuser can rename a database;
non-superuser owners must also have the CREATEDB privilege.
Looks like a superuser must have CREATEDB too:
[EMAIL PROTECTED] SELECT usesuper, usecreatedb from pg_user where usename =
'fduch';
usesuper | usecreatedb
The following bug has been logged online:
Bug reference: 5891
Logged by: Alexander V. Chernikov
Email address: melif...@ipfw.ru
PostgreSQL version: 8.4.5
Operating system: FreeBSD 7.3
Description:Unique index is not unique
Details:
Just in case if formatting is
86 matches
Mail list logo
