I am using postgresql as database server in my VB
application. I use DAO(ODBCDirect) to connect to the database. It works with
postgresql 7.1.x before.
When I upgraded the postgresql to 7.2.1, I found that
the program does not work with the new version. The program gets DAO
RecordSet from
Hi,
I hit an issue running PG 8.2.3 with the continuous archiving feature
where I was unable to recover from the backup. I was wondering if
this may be related to bug #3245?
These are the steps that occurred before I saw this problem:
1. Prepare transaction.
2. A base backup of the database w
onally selecting
> the "Factory" zone?
I don't think I've put the correct timezone file in /etc/localtime so
it is using some default file from the Gentoo install.
John
On Mon, Jun 30, 2008 at 12:26 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "John Smith" &l
Russell Smith wrote:
> Hi,
>
> After experiencing a seg fault on RHEL5's command line php, I did the
> following investigation.
>
> As I dot not have a RHEL5 box available with debugging tools, I
> reproduced the bug on CentOS5.
Hi,
I've not received any feedback on
t reaches 0 then
call CRYPT_set_xx_callback(NULL) to remove the callbacks. This is a
windows SSL thread that crashes iexplore and testifies to the same
problem http://www.mail-archive.com/[EMAIL PROTECTED]/msg53869.html
Thoughts?
Regards
Russell Smith
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[EMAIL PROTECTED] wrote:
> select ats.id, ap.value from akh_test_suit ats
> LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
> where ats.ID = 472
>
> id | value
> 472 | 472
> ID -- integer
> value -- text
>
>
> select * from akh_test_suit ats
> LEFT JOIN akh_properties ap on ap.ID
Hemavathi B N wrote:
> The following bug has been logged online:
>
> Bug reference: 4393
> Logged by: Hemavathi B N
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: windows 2003
> Description:failed toget system metics for terminal servic
I have just run into this issue myself and I was wondering if it is
considered a bug or a missing feature? Is there a plan to address this
in an upcoming release? Has anyone found a good work around to the
problem in the interim?
Thanks!
John.
On Wed, May 7, 2008 at 4:38 AM, Marshall, Steve <[EMA
The following bug has been logged online:
Bug reference: 4717
Logged by: Andrew Smith
Email address: laconi...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Windows XP
Description:Installing PostGIS via StackBuilder gives an 'Error
opening file' err
The following bug has been logged online:
Bug reference: 5015
Logged by: Ken Smith
Email address: kensm...@adobe.com
PostgreSQL version: 8.4
Operating system: Windows
Description:MySQL migration wizard does not start
Details:
I have downloaded and installed
: Ashesh Vashi [mailto:ashesh.va...@enterprisedb.com]
Sent: Thursday, August 27, 2009 7:31 AM
To: Ken Smith
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #5015: MySQL migration wizard does not start
Hi Ken Smith,
We found that - the jar files, we packaged with the installers are corrupted
Annita Veneti wrote:
> Matt you are absolutely right! The msysconf is not related...
> Yesterday I did some test and have seen that the access is working fine with
> postgres as long as the SSL mode is disable, as soon as I put it enabled then
> it crashes on shutdown
>
> Go figure!!!
>
> Any
ty, so a
source build may be the only good route to get a newer version onto there.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
tep of the build the last
time. If you're not sure exactly how the old one was built, this can
help you out.
--
Greg Smith2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-bugs mailing list (pgsql-bug
Michail Antonov wrote:
> The following bug has been logged online:
>
> Bug reference: 5319
> Logged by: Michail Antonov
> Email address: atin65...@gmail.com
> PostgreSQL version: 8.4.2
> Operating system: Windows XP
> Description:recursion in the triggers
> Details:
>
Hi,
I've recently upgraded to PostgreSQL 8.4 as Redhat had begun supporting
it. I have tried to dump database grants, but have only found an
obscure way to do it.
I would expect;
postgres$ pg_dump -Fc database_name > backup.pgdump
would include all of the GRANT CONNECT on database_name TO "Rol
On 02/05/10 01:36, Tom Lane wrote:
> Russell Smith writes:
>
>> Is this considered a bug that the only way to do a dump/restore with
>> database privileges is to use pg_dumpall?
>>
> No, that's the intended place for them given the current divisio
On 03/05/10 01:30, Tom Lane wrote:
> Russell Smith writes:
>
>> On 02/05/10 01:36, Tom Lane wrote:
>>
>>> No, that's the intended place for them given the current division of
>>> labor between pg_dump and pg_dumpall. There have been complai
Hi,
pg_restore silently ignores the inclusion of -C when you do use a
restore list.
postgres$ pg_dump -Fc postgres > postgres.dump
postgres$ pg_restore -C postgres.dump | grep 'CREATE DATABASE'
CREATE DATABASE postgres WITH TEMPLATE = template0 ENCODING = 'UTF8';
## Create a restore list
postgre
On 13/05/10 03:39, Tom Lane wrote:
> Russell Smith writes:
>
>> pg_restore silently ignores the inclusion of -C when you do use a
>> restore list.
>>
> It would work as you expect if you use -C when creating the list file.
> The reason for this is that -C b
On 13/05/10 19:26, Russell Smith wrote:
> On 13/05/10 03:39, Tom Lane wrote:
>
>> Russell Smith writes:
>>
>>
>>> pg_restore silently ignores the inclusion of -C when you do use a
>>> restore list.
>>>
>>>
>>
On 15/05/10 03:26, Tom Lane wrote:
> Russell Smith writes:
>
>>> By the operation of other items (-C --data-only) passed with -l, it only
>>> produces to contents that would be restored with the other switches
>>> provided. If that's expect behavior, th
On Fri, Mar 10, 2000 at 09:01:15AM +0100, Kardos, Dr. Andreas wrote:
> Of course, Digital Unix is more important than QNX. For now I can live with
> the solution to remove the escape backslashes from pg_dumpall.
> But we should keep this problem in mind. Unix portable shell programming is
> not a
POSTGRESQL BUG REPORT TEMPLATE
Your name :Richard Smith
Your email address : [EMAIL
Hi People,
I have encountered the following problem with pg_dump from postgresql
7.0.2 on linuxppc:
bash $ pg_dump template1 >tp.db
getFuncs(): SELECT failed. Explanation from backend: 'ERROR:
getattproperties: no attribute tuple 1255 -2'.
CONFIGURATION
machine: PowerMac Rev2 B/W G3 450, 256M
I believe I have found a bug. I don't know whether the bug is with
PostgreSQL, MySQL, or the SQL specification. Please help me to
understand what I have. Thank you.
THE TEST SYSTEM
PostgreSQL version: 7.0.2
Platform: PentiumIII550x2, 512MB SDRAM, Linux2.2.13, glibc-2.1.2
[ken@ken ken]$ ldd /usr
I'm building a 3-dimensional array using 5 tables; 3 of them define the
headings for the 3 dimensions, a fourth states the valid combinations
of labels, and the 5th table matches combinations to values.
I want to populate the first 4 tables all at the same time; by providing
the grid which define
Tigran Mkrtchyan wrote:
Does it mean that I have to commit after each select statement?
Here what the manual says:
Description
COMMIT commits the current transaction. All changes made by the
transaction become visible to others and are guaranteed to be durable
if a crash occurs.
The following bug has been logged online:
Bug reference: 3041
Logged by: Matt Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Mac OS X
Description:Universal Binary Support in Configure
Details:
Hello! From what I can tell, there
Tom Lane wrote:
"Jens-Wolfhard Schicke" <[EMAIL PROTECTED]> writes:
I an explain analyze I saw recently, a BitmapOr node of 5 Bitmap Index Scan
looked like this:
BitmapOr (cost=43.57..43.57 rows=1833 width=0) (actual time=0.146..0.146
rows=0 loops=1)
Can we do better than just sayi
Alvaro Herrera wrote:
Jeff Davis wrote:
CREATE ROLE test_role
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
CREATE ROLE invalid_grantor
SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
SET ROLE invalid_grantor;
GRANT "postgres" TO "test_role";
SET ROLE postgres;
select * from pg_roles;
Alvaro Herrera wrote:
Russell Smith wrote:
Alvaro Herrera wrote:
Jeff Davis wrote:
CREATE ROLE test_role
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
CREATE ROLE invalid_grantor
SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
SET ROLE invalid_grantor;
GRANT "postgre
Russell Smith wrote:
CREATE ROLE test_role
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
CREATE ROLE invalid_grantor
SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
SET ROLE invalid_grantor;
GRANT "postgres" TO "test_role";
SET ROLE postgres;
select * from pg_roles;
se
Alvaro Herrera wrote:
Russell Smith wrote:
As I am not a frequent reporter of bugs, what happens now? It's been a
week since I wrote my last message and I'm unsure of whether anything
has, or is going to happen about this bug report. Alvaro has said it's
a "bug&
by any role, as
if you drop and recreate the object you can achieve this anyway.
Regards
Russell Smith
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
The following bug has been logged online:
Bug reference: 3265
Logged by: Russell Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: RHEL4
Description:8.1 -> 8.2 behviour change: View owner must have access
to underlying tables
Deta
Tom Lane wrote:
"Russell Smith" <[EMAIL PROTECTED]> writes:
CREATE view v1 as select * from t1;
ALTER TABLE v1 OWNER TO "USER";
See thread here:
http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
and patch here:
http://archives.postgresql.or
Alvaro Herrera wrote:
Alvaro Herrera wrote:
2. decide that the standard is braindead and just omit dumping the
grantor when it's no longer available, but don't remove
pg_auth_members.grantor
Which do people feel should be implemented? I can do whatever we
decide; if no one has a stro
Alvaro Herrera wrote:
Alvaro Herrera wrote:
Alvaro Herrera wrote:
2. decide that the standard is braindead and just omit dumping the
grantor when it's no longer available, but don't remove
pg_auth_members.grantor
Which do people feel should be implemented? I can do whatever we
Alvaro Herrera wrote:
Russell Smith wrote:
Alvaro Herrera wrote:
Alvaro Herrera wrote:
2. decide that the standard is braindead and just omit dumping the
grantor when it's no longer available, but don't remove
pg_auth_members.grantor
Which do people feel
Heikki Linnakangas wrote:
Randolf Richardson wrote:
After convincing clients and colleagues to switch from Oracle (and others)
to PostgreSQL, an issue that comes up is the need to customize DATESTYLE.
Because this isn't possible, the developers who were against the move to
PostgreSQL make
Alvaro Herrera wrote:
Russell Smith wrote:
The issue is output, not input.
SET datestyle='dmy';
SELECT '03-03-2004'::date
Will return '2007-03-03', not 03-03-2004 as is the set datestyle.
You are aware that DateStyle controls both input and output,
_separatel
ormations do not guarantee that y > 1.5x == y/x >
1.5. This is only true for x>0, y < 1.5*x for x<0. I have not posted a
patch as I'm not sure what is the best way to change the example.
Regards
Russell Smith
---(end of broadcast)
Tom Lane wrote:
Russell Smith <[EMAIL PROTECTED]> writes:
In-equality transformations do not guarantee that y > 1.5x == y/x >
1.5. This is only true for x>0, y < 1.5*x for x<0. I have not posted a
patch as I'm not sure what is the best way to change the examp
The following bug has been logged online:
Bug reference: 4089
Logged by: John Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Linux 2.6.20-gentoo-r8
Description:When available disk space is low pg_stop_backup() fails,
as do
On Fri, Apr 4, 2008 at 7:46 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "John Smith" <[EMAIL PROTECTED]> writes:
> > Steps to reproduce:
> > -- start with a running PG instance with WAL archiving enabled
> > -- select pg_start_backup('tes
gsql.php:3
Stack trace:
#0 /root/test-pgsql.php(3): PDO->__construct('pgsql:host=thoe...', 'nouser',
'nopass')
#1 {main}
thrown in /root/test-pgsql.php on line 3
As a result, the crash has gone away. Are the comments in the PHP
comment accurate and is it re
When I try to delete data from one table, I get this error:
ERROR: get_typdefault: failed to lookup type 0
I can't find any reasons other than a bug. The PG version is 7.3.4
Get advanced SPAM filtering on Webmail or POP Mail ... Get
Thanks both for your response. Here is a screen shot with the table definition and
reproducible example:
mm=# \d signon
Table "public.signon"
Column | Type | Modifiers
-+---+---
name| character varying(25) | not null
user_id
this form.
POSTGRESQL BUG REPORT TEMPLATE
Your name : Russell Smith
Your email address : As From address
System Configuration
-
Architecture (exam
On Sat, 13 Nov 2004 04:05 pm, Tom Lane wrote:
> Russell Smith <[EMAIL PROTECTED]> writes:
> > pg_dump does not fold case, and quote table and schema names correctly.
>
> This is not a bug; it is a behavior we deliberately adopted years ago,
> after unsuccessful experiments
The following bug has been logged online:
Bug reference: 1547
Logged by: John Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000
Description:CREATE TYPE AS error
Details:
When trying to create a complex type, the parser
I re-installed postgresql as a service and CREATE TYPE AS works. So I then
re-installed postgresql as a program (as I had originally done) and CREATE
TYPE AS doesn't work.
Perhaps you could check this on your system.
John Smith
--
AIL PROTECTED]>
Reply-To: pgsql-bugs@postgresql.org
To: John Smith <[EMAIL PROTECTED]>
CC: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #1547: CREATE TYPE AS error
Date: Sat, 2 Apr 2005 19:23:45 -0700
On Mon, Mar 28, 2005 at 12:51:42AM +, John Smith wrote:
> I re-installed po
f anything needs to be changed here, it's the behavior of round(numeric).
>
So I would say that the round behaviour has changed as Tom has suggested, but
which is correct?
7.2, or 8.0?
Regards
Russell Smith
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
t.propname = 'T' THEN 'Err'
> WHEN t.propname = 'U' THEN 'Rm'
> WHEN t.propname = 'V' THEN 'Tm'
> WHEN t.propname = 'W' THEN 'Tm'
> ELSE t.propname
> END as
immediately). While we'd like to accept it, we have
> not figured out a rule that doesn't break the spec in other ways.
> For now I'd recommend casting the NULLs explicitly.
Can we spit out an error that is slightly more relevant? Maybe print
a wa
The following bug has been logged online:
Bug reference: 1781
Logged by: Andrew Smith
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: Debian GNU/Linux 3.1
Description:result of cascading triggers not available until
function exits
Nicholas wrote:
The following bug has been logged online:
Bug reference: 1993
Logged by: Nicholas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3,8.0.4,8.1
Operating system: Gentoo Linux
Description:Adding/subtracting negative time intervals changes time
z
on Name: customers +
Alias: customers +
Startup Cost: 0.00 +
Total Cost: 726.00 +
Plan Rows: 19000 +
Plan Width: 268+
Filter: (customerid > 1000)
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL T
+
Seq Scan +
Outer+
customers+
customers+
0.00 +
726.00 +
19000+
268+
(customerid > 1000) +
+
+
+
+
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.us
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 15/05/10 05:15, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of vie may 14 13:26:06 -0400 2010:
>
>
>> However, I think -C is a special case because it's quite un-obvious
>> to the user that it effectively acts as a filter switch --- in fact a
>> de-filtering switch, because the l
The following bug has been logged online:
Bug reference: 6059
Logged by: Perry Smith
Email address: pedz...@gmail.com
PostgreSQL version: 9.0.4
Operating system: AIX 5.3 and Mac 10.6.7
Description:Out of tree build fails using Make 3.82
Details:
The failure is
that setting shared_buffers so high
on Linux is more likely to slow the server than speed it up, which you
said you didn't want to discuss. Just pointing it out so no one else
gets the wrong idea from your configuration.)
--
Greg Smith 2ndQuadrant USg...@2ndquadrant.com B
nt.
It's hard to justify making a change that will produce less accurate
results in the vast majority of cases, just to improve behavior in a
situation where useless results are coming out no matter what.
--
Greg Smith 2ndQuadrant USg...@2ndquadrant.com Baltimore, MD
PostgreSQL Tra
POSTGRESQL BUG REPORT TEMPLATE
Your name : Steven Smith
Your email address : [EMAIL
Sorry, never mind. The semi-colon key on the keyboard
being used does not function correctly.
Eddie
- Original Message -
From: Eddie J.
Smith
To: [EMAIL PROTECTED]
Sent: Wednesday, March 12, 2003 1:52 PM
Subject: DROP TABLE
Hello,
I think this must be a bug, because I can&#
Hello,
I think this must be a bug, because I can't drop any of my
tables in PostgresQL v. 7.3.2, which seems strange because I'm sure it would
have been tested or reported?
Thank you,
Eddie
68 matches
Mail list logo
