[BUGS] Error number -2147467259 with driver PgOleDb
Hi, We are developing a system with PostgreSQL in Windows through VB application. We are getting the following error while save records. Description: Unhandled status in query result Err Number: -2147467259 Source: PgOleDb (This error is occuring everytime after the 270 -300 record saved) Can somebody help me in this? Ing. Hugo C Ponce Suárez Universidad de Colima Dpto de Inv. y Desarrolo de SIABUC Mexico ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] extra columns in intermediate nodes not being removed by top level of executor
On Sat, Sep 03, 2005 at 04:29:25PM -0400, Allan Wang wrote: > I'm using 8.1 from CVS head of about two days ago. > > Extra columns seem to be on sum(plays.length), videos.path, videoid Here's a simplified, complete test case: CREATE TABLE foo ( x integer, y integer ); INSERT INTO foo (x, y) VALUES (1, 2); SELECT * FROM (SELECT sum(x), (SELECT y) AS yy FROM foo GROUP BY y) AS s LIMIT 1; sum | yy | -++--- 1 | 2 | 2 (1 row) SELECT * FROM (SELECT sum(x), (SELECT y) AS yy FROM foo GROUP BY yy) AS s LIMIT 1; sum | yy -+ 1 | 2 (1 row) SELECT * FROM (SELECT sum(x), (SELECT y) AS yy FROM foo GROUP BY y) AS s; sum | yy -+ 1 | 2 (1 row) SELECT * FROM (SELECT sum(x), y AS yy FROM foo GROUP BY y) AS s LIMIT 1; sum | yy -+ 1 | 2 (1 row) SELECT * FROM (SELECT x, (SELECT y) AS yy FROM foo) AS s LIMIT 1; x | yy ---+ 1 | 2 (1 row) -- Michael Fuhr ---(end of broadcast)--- TIP 1: 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
[BUGS] extra columns in intermediate nodes not being removed by top level of executor
I'm using 8.1 from CVS head of about two days ago.
Extra columns seem to be on sum(plays.length), videos.path, videoid
create or replace view niceplays as SELECT count(*) AS plays,
summary("substring"(v.path, '[^/]+$'::text), 50) AS filename,
avg(p.length)::interval(0) AS avg, sum(p.length)::interval(0) AS sum,
(( SELECT now() - plays.playtimestamp
FROM plays
WHERE plays.videoid = v.videoid
ORDER BY plays.playid DESC
LIMIT 1))::interval(0) AS lastplay
FROM plays p
LEFT JOIN videos v USING (videoid)
WHERE p.length <> '00:00:00'::interval AND v.path ~~
'/home/allan/TransGaming_Drive/libp/%'::text
GROUP BY v.path, v.videoid
ORDER BY sum(p.length::interval(0)) DESC;
allan=# select * from niceplays;
plays | filename | avg| sum| lastplay
---+--+--+--+-
13 | | 00:06:07 | 01:19:26 | 20 days 18:33:51
8 | | 00:07:18 | 00:58:23 | 17 days 23:49:38
8 | | 00:04:13 | 00:33:44 | 31 days 22:55:20
3 | | 00:10:56 | 00:32:47 | 17 days 00:04:18
7 | | 00:04:34 | 00:32:00 | 31 days 22:55:36
6 | | 00:05:04 | 00:30:22 | 17 days 23:46:32
[...]
(868 rows)
allan=# select * from niceplays order by sum desc limit 3;
plays | filename | avg| sum| lastplay | | |
---+--+--+--+--+--+-+-
13 | | 00:06:07 | 01:19:26 | 20 days 18:35:59 | 01:19:26 | | 43
8 | | 00:07:18 | 00:58:23 | 17 days 23:51:47 | 00:58:23 | | 1988
8 | | 00:04:13 | 00:33:44 | 31 days 22:57:29 | 00:33:43 | | 1961
Allan Wang
---(end of broadcast)---
TIP 1: 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
Re: [BUGS] BUG #1860: Insert failed due to unique index
Viswanath Ramineni wrote: > I have a table with a primary key on id (integer) column and a unique > index on varchar(10) column. Insertion fails when the value of the > unique column is substring of an existing value. For example, if I > have a row with the unique column value 'TEST1', it will not allow me > insert another row with 'TEST' as the value for this column. Please show the exact sequence of commands that leads to this situation. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #1861: Possible Incompatibly with NOD32 AV.
I would contact the people who created NOD32, give them the URL to pginstaller, and tell them it breaks PostgreSQL. --- Thomas Turn Jensen wrote: > > The following bug has been logged online: > > Bug reference: 1861 > Logged by: Thomas Turn Jensen > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.3 > Operating system: Windows XP SP2 > Description:Possible Incompatibly with NOD32 AV. > Details: > > I'm aware this will not be a "complete" bug report with all neccesary > information. I have not tried to reproduce the problem but am satisfied I > found a solution. The reason I make this bug report is a result of someone > (rightly) saying "im not sure who you would mail but i think it needs > documenting.." after the fact. Since I know of no better means of > documenting it, I use this approach. > > > PROBLEM: > After installing NOD32 antivirus (www.nod32.com) PostgreSQL no longer > works. > > SYMPTOMS: > Any application trying to connect/log into PG freezes. Only a termination of > the PG service will unfreeze the applications with an error about unexpected > EOF from socket (or something to that effect. Sorry, I don't have the exact > message). > > Log in pg_log/postrgresql-#date-#postfix contains the following entries for > every frozen application: > 2005-09-03 02:46:11 LOG: could not receive data from client: No connection > could be made because the target machine actively refused it. > 2005-09-03 02:46:11 LOG: incomplete startup packet > > POSSIBLE MITIGATING FACTORS: > NOD32 was installed together with PC-cillin 2002 (AV). However only NOD32 > was active. Disabling NOD32 did not have any effect. > "Google Desktop" reports possible conflicts with NOD32. > > WORKARROUND: > After uninstalling NOD32 and rebooting, PG works as expected. > > SELECT version(): > PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 > (mingw-special) > > ---(end of broadcast)--- > TIP 1: 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 > -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (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 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[BUGS] BUG #1861: Possible Incompatibly with NOD32 AV.
The following bug has been logged online: Bug reference: 1861 Logged by: Thomas Turn Jensen Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Windows XP SP2 Description:Possible Incompatibly with NOD32 AV. Details: I'm aware this will not be a "complete" bug report with all neccesary information. I have not tried to reproduce the problem but am satisfied I found a solution. The reason I make this bug report is a result of someone (rightly) saying "im not sure who you would mail but i think it needs documenting.." after the fact. Since I know of no better means of documenting it, I use this approach. PROBLEM: After installing NOD32 antivirus (www.nod32.com) PostgreSQL no longer works. SYMPTOMS: Any application trying to connect/log into PG freezes. Only a termination of the PG service will unfreeze the applications with an error about unexpected EOF from socket (or something to that effect. Sorry, I don't have the exact message). Log in pg_log/postrgresql-#date-#postfix contains the following entries for every frozen application: 2005-09-03 02:46:11 LOG: could not receive data from client: No connection could be made because the target machine actively refused it. 2005-09-03 02:46:11 LOG: incomplete startup packet POSSIBLE MITIGATING FACTORS: NOD32 was installed together with PC-cillin 2002 (AV). However only NOD32 was active. Disabling NOD32 did not have any effect. "Google Desktop" reports possible conflicts with NOD32. WORKARROUND: After uninstalling NOD32 and rebooting, PG works as expected. SELECT version(): PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special) ---(end of broadcast)--- TIP 1: 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
Re: [BUGS] BUG #1858: setting search path in select doesn't (always) work
Hi list, I reported the bug because I was convinced it was something fishy, however, the bug I reported proved to be something completely else. I don't even know if it is a bug at all. If you do a set search_path; the path is set correctly according to the rules of autocommit and everything else. If however you are not authorized to use the schema, the next query on a table within the requested schema results in a table not found condition, which makes sense, because it actually cannot find the table, because it cannot enter the schema. I have checked the way psycopg handles this, and if a select is done on the table this is working correctly, File "/home/dick/CVix/CVix/src/ObjectBuilder.py", line 516, in __BldTabDef cur.execute(Sqlstmt) psycopg.ProgrammingError: ERROR: permission denied for schema adeuxproductie Select * from "adeuxproductie"."parameters" WHERE 1=0 so the problem must be within Zope and I will report this problem to the Zope community. Thanks for all your help. Op vrijdag 2 september 2005 17:12, schreef Michael Fuhr: > On Fri, Sep 02, 2005 at 10:58:12AM -0400, Tom Lane wrote: > > "D.J. Kniep" <[EMAIL PROTECTED]> writes: > > > After setting the search path the query > > > Select * from vwexternetoegang > > > produces the required results in the first installation, but in the new > > > installation, it cannot find the view. However, if I do an explicit > > > Set search_path to "testschema"; > > > it works as expected. > > > > What does "show search_path" report in the failing and non-failing > > states? Also try "select current_schemas(true)". > > This thread came up in pgsql-general yesterday; Dick says the real > problem was something else. > > http://archives.postgresql.org/pgsql-general/2005-09/msg00074.php Cheers, Dick Kniep ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[BUGS] BUG #1860: Insert failed due to unique index
The following bug has been logged online: Bug reference: 1860 Logged by: Viswanath Ramineni Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Beta Operating system: Windows 2000 Professional Description:Insert failed due to unique index Details: I have a table with a primary key on id (integer) column and a unique index on varchar(10) column. Insertion fails when the value of the unique column is substring of an existing value. For example, if I have a row with the unique column value 'TEST1', it will not allow me insert another row with 'TEST' as the value for this column. ---(end of broadcast)--- TIP 6: explain analyze is your friend
