""P.P.S. Narayan"" <[EMAIL PROTECTED]> wrote
>
> However, there are a bunch of http requests that come in after the hanging
> request, which get deadlocked on the locks held by the hanging request. AS
> far as I have read, there is a lock_timeout parameter in postgresql config
> file to timeout af
<[EMAIL PROTECTED]> wrote
>
> Recently I facing one problem, when the connection for postgresql grow
> up
> to 45 or more, when I trigger a statement from WebApp
> this statement will stuck forever.
> I try to kill this transaction and then trigger the same statement
> again
> but it still the s
""Carmen"" <[EMAIL PROTECTED]> wrote
>
> I have a Windows system accesing a FreeBSD PostGres 8.0.
> I have a multihread process in Windows using a PostGres 8.0 FreeBSD. Each
> thread of this process has a TCP communicaction with a remote client and
it
> updates a common BD of the global process.
>
""Peter Brant"" <[EMAIL PROTECTED]> wrote
>
> I'm afraid we're in the same category as everyone else with no good way
> to reproduce the bug, but is there anything else we could do if this
> happens again?
>
There is a "Win32 semaphore patch" in the patch list, but we are lack of
evidence to prov
""Peter Brant"" <[EMAIL PROTECTED]>
>
> In the last couple of days, we've been bitten (a couple of times, on
> different servers) by an apparent glitch or bad interaction in the
> Windows implementation of rename().
>
> The relevant log message is:
>
> [2006-04-17 16:49:22.583 ] 2252 LOG: could n
""Peter Krauss"" <[EMAIL PROTECTED]> wrote
>
> The single query (on psql) is fary fast
> (less than 1 sec)
>
> SELECT a,b,c,d FROM products_view WHERE
> sku='0-123-0-0-6024-20'
> OR lower(codfornecedor)=lower('0-123-0-0-6024-20')
> OR lower(eanfor)=lower('0-123-0-0-6024-20')
> OR lower(refpro
""Brock Peabody"" <[EMAIL PROTECTED]> wrote
>
> Do you think this is a Windows only problem?
>
I am afraid so. We have received 3 reports of this (or quite similar)
problem, all in 8.1/windows. I just noticed that yours is actually an EAGAIN
error, so the loop patch in semctl() doesn't work I gue
<[EMAIL PROTECTED]> wrote
> In "g_int_compress" :
>
>
> int*dr;
> ...
> memmove((void *) &dr[cand - 1], (void *) &dr[cand + 1], (len - cand -
> 1) * sizeof(int));
>
> Should be
>
> int32 *dr;
> ...
> memmove((void *) &dr[cand - 1], (void *) &dr[cand + 1], (len - cand -
> 1)
""Brock Peabody"" <[EMAIL PROTECTED]> wrote
>
> FATAL: semctl(167894456, 4, SETVAL, 0) failed: A non-blocking socket
> operation could not be completed immediately.
>
Can you reliablly reproduce the problem? If so, we may come up with a
testing patch to it. We encounter similar problems before b
"Tom Lane" <[EMAIL PROTECTED]> wrote
> "Qingqing Zhou" <[EMAIL PROTECTED]> writes:
> > The problematic line is "0 written" --
>
> What's your point? Those stats are correct for the current process (or
> if not, better take it u
test=# set log_statement_stats = on;
SET
test=# checkpoint;
LOG: QUERY STATISTICS
DETAIL: ! system usage stats:
! 0.100725 elapsed 0.00 user 0.00 system sec
! [0.00 user 0.001999 sys total]
! 0/0 [0/0] filesystem blocks in/out
!
""Sudhakar"" <[EMAIL PROTECTED]> wrote
>
>
> we are getting the following error while execute select querry.
>
> airlinklive=# select * from ctcasetrack;
> ERROR: Invalid page header in block 1391 of ctcasetrack
>
Page #1391 is corrupted. Check out the following thread to see if you can
save som
I encounter a server(8.1.1) problem like this:
create table tt(id int);
prepare p1(int) as insert into tt values($1);
execute p1(3);
alter table tt alter id type char(10);
execute p1(999);
select * from tt;
^ server core dumps here
Command "execute p1(999)" wor
On Tue, 28 Feb 2006, Bruce Momjian wrote:
>
> Uh, how do we handle it now? I thought we did just that.
>
> OK, so how do we find the answer?
>
For both problems, I am uncertain (or I've sent a patch already :-(). Call
more artillery support here ...
Regards,
Qingqing
"Bruce Momjian" wrote
> > In port/win32.h, we have
> >
> > #undef EAGAIN
> > #undef EINTR
> > #define EINTR WSAEINTR
> > #define EAGAIN WSAEWOULDBLOCK
> >
> > What's the rationale of doing so?
>
> We did this so that our code could refer to EINTR/EAGAIN without
> port-specific tests.
>
AFAICS, b
""herianto"" <[EMAIL PROTECTED]> wrote
>
> Every I will query select * from namaTable , I get Error invalid page
> header. but if me use query select * from namaTable limit 1008. I get
Query
> is successfully.
>
> Total rows of tables is 1009. while if me query select * from namaTable
> limit 10
I encountered an error when I fast shutdown 8.1.1 on Win2k:
FATAL: semctl(1672698088, 12, SETVAL, 0) failed: A blocking operation
was interrupted by a call to WSACancelBlockingCall.
A similar error on 8.1/win2003 was reported on pgsql-general (sorry, I can't
dig out the
original post fr
""Steven Mooij"" <[EMAIL PROTECTED]> wrote
>
>
> Tried to copy the result of a join into another table, about 45.000.000
> (small) records. This is the result:
>
> testsearch=> insert into t_documentword2 (SELECT document_id, t_word2.id,
> frequency from t_documentword, t_word2 where t_documentwor
""Sunil Basu"" <[EMAIL PROTECTED]> wrote
>
> Previously I used to insert records into the postgresql database
> unconditionally. That is everytime a data comes it is stored in the
> postgresql. So I land up with some redundant data always.
> But the operation was smooth and near about 600 records
""Carlos del Cacho"" <[EMAIL PROTECTED]> wrote
>
> The following bug has been logged online:
>
> Bug reference: 2135
> Logged by: Carlos del Cacho
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.1
> Operating system: Win2k
> Description:system error 182 wh
""Wojciech Sobczuk"" <[EMAIL PROTECTED]> wrote
>
> I have a 16GB database which is very busy (100 requests per second).
> After
> running for some time (sometimes 2 days sometimes longer sometimes
> shorter)
> postgres hangs.
Can you follow the steps in this thread to find out what's going on o
"wangshj" <[EMAIL PROTECTED]> wrote
>
> oidtest=# COPY oidtest (name) WITH OIDS FROM stdin;
> Enter data to be copied followed by a newline.
> End with a backslash and a period on a line by itself.
>>> 54513copyname
>>> \.
> oidtest=# INSERT INTO oidtest ( name ) VALUES( 'name2' ) ;
> INSE
"Joost Kraaijeveld" <[EMAIL PROTECTED]> wrote
>
> select objectid,defaulttermsofpayment from prototype.customers
> where
> objectid = '336A0451-D9E8-7C11-6333-C17DF18E8979'
>
> I get the following answer:
>
> "336A0451-D9E8-7C11-6333-C17DF18E8979";"null"
>
test=# create table m (c1 char(10), c2 c
On Wed, 23 Nov 2005, Harald Armin Massa wrote:
>
> no, it is definitely NOT a temp table. I know which table it is,
> because: that "could not open relation ..." error message was exactly
> provokable with "select * from repofeld", which is one of my tables in
> that database.
>
What is your file
""neeraj chaudhari"" <[EMAIL PROTECTED]> wrote
>
> FATAL: unsupported frontend protocol
> FATAL: unsupported frontend protocol
> FATAL: unsupported frontend protocol
>
> Then to i am able to connect to the database & access & modify the
> records.
>
It looks like your client guesses out the r
"Harald Armin Massa" <[EMAIL PROTECTED]> wrote
>
> 2005-11-21 09:45:50 ERROR: could not open relation 1663/17253/43471: No
> such
> file or directory
>
> My checking showed that... within directory data/base/17253 there is
> indeed
> no file named 43471; but ones named 43470,43472,43473 .
>
""Acure"" <[EMAIL PROTECTED]> wrote
>
>
> As pgsql user i execute initdb :
>
> "initdb -U pgsql -W -D datapl"
>
>
>
> and it stop on :
>
> "creating template1 database in tescik/base/1 ..."
>
Why you set "datapl" as the data directory but you get a "tescik"? Also, to
see where it stops,
""Dragon"" <[EMAIL PROTECTED]> wrote
>
> When I install postgresql server,I can not find the chinese charactor
> GB2312
> or GBK or GB18310 , and In the pgAdmin III when I create a database, in
> the
> Dialog I can not select Encoding GBK or other Chinese Encoding,
> "A error orccured
> Error :G
On Wed, 9 Nov 2005, Tomasz Ostrowski wrote:
>
> Using "char*" as an argument type instead of "const char*" in ecpglib.h
> causes that for example the following sample program, basically
> copied from docmentation
> http://www.postgresql.org/docs/8.1/interactive/ecpg-dynamic.html ,
> does not comp
""wgh"" <[EMAIL PROTECTED]> wrote
>
> I use PowerBuilder8.0, i use ODBC to connect postgers8,i was in china,i
> use
> chinese, it have datawindow error :fetch item error!!
>
Does ODBC returns any non SQL_SUCCESS information? To find it out, enable
the ODBC trace log and search for it.
Regards,
"Valery Bondarenko" <[EMAIL PROTECTED]> wrote:
> Situation first occurs on _CLEAN_ Win2k server with 8.0.0 Installed by his
> installer (woops :) ).
> And it continues to...
> Also I got it in a realy "dirty" environment with 8.1.
>
> But in both cases there were no antiviruses and (AFAIK) no prod
"Tom Lane" <[EMAIL PROTECTED]> wrote
>> When the cluster performs a massive disk operations (like nightly
>> vacuuming or smth)
>> I offten got such error in log file:
>> 2005-11-12 14:52:29 LOG: could not fsync segment 0 of relation
>> 1663/17735/210608: Permission denied
>
>> It looked like as i
"Rob Prowel" <[EMAIL PROTECTED]> wrote
> two almost identical queries: one searches for
>
> read in ('N','n')
>
> and the other searches for
>
> read in ('Y','y').
>
> the (explain) SQL statement says that one uses the
> index on the (read) field and the other does a
> sequential table scan. Why!
"Tom Lane" <[EMAIL PROTECTED]> wrote
>
> Works fine for me in Fedora Core 4. Something broken about your
> platform, is my guess ...
>
You may want to talk to our system admin :-) ... but it doesn't look like
caused by some strange environment ...
/h/164/zhouqq/pginstall/bin#uname -a
Linux eon.
I do "make PROFILE=-pg" on top level, seems everything is ok. When
postmaster starts up, gmon.out is generated. But when I do use psql to
connect to postmaster, a repeatable segment fault happens no matter what
command you do in psql:
sh-2.05a$ psql test
Welcome to psql 8.1RC1, the PostgreSQL int
--- Sample output ---
$/bin/data#more postmaster.opts
*/bin/postgres -D data
$/bin/data#cd ..
$/bin#pg_ctl -Ddata start
postmaster starting
$/bin#LOG: database system was shut down at 2005-10-27 03:17:17 EDT
LOG: checkpoint record is at 0/33AE4C
LOG: redo record is at 0/33AE4C; undo record is at
""Jeff Tong"" <[EMAIL PROTECTED]> wrote
>
> The following bug has been logged online:
>
> Bug reference: 1985
> Logged by: Jeff Tong
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1beta3
> Operating system: Windows XP
> Description:cannot insert Chinese cha
""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote
> Turning off the antivirus fixed the problem.
> We haven't have any read/write/open error in more
> than two days.
>
> Thank you very much for your help and keep up the good work.
>
You are welcome :-) But I still suspect if this really solves
""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Yes, there is an antivirus software on the machine, a reboot is needed
> when it's turned off,
> I'll be allowed to reboot it tonight or I'll do it sooner if it crashes
> before that.
>
> There are around
""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote
>
> I've installed PostgreSQL 8.1 beta2 five days ago and it crashed 3 times
> since then.
> Here is what's been logged for the last crash
>
> 2005-10-04 11:00:19 FATAL: could not read block 121 of relation
> 1663/16384/2608: Invalid argument
""tk"" <[EMAIL PROTECTED]> wrote >
> The following bug has been logged online:
>
> Bug reference: 1856
> Logged by: tk
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.0.3
> Operating system: linux
> Description:chinese sort error
> Details:
>
> chinese sort e
My theory is "select;" incurs a parse error and this error message is
supposed to be translated into your encoding, but unfortunately not every
UTF8 character is necessarily be encoded as GB18030, which will cause an
infinite recursive elogs just like this:
1:elog(parse_error)// contain u
"Qingqing Zhou" <[EMAIL PROTECTED]> writes
> If we concurrently perform drop/create table (with foreign keys) commands
> several times, we could corrupt the pg_trigger system table.
>
Anybody reproduced it?
Regards,
Qingqing
---
Pg7.4.x does not have a native win32 support. You can install it from cygwin
or download the latest stable version 8.0.2 (recommended).
Regards,
Qingqing
"ÍõÁÁ" <[EMAIL PROTECTED]> дÈëÓʼþ
news:[EMAIL PROTECTED]
Hello:
I download the postgresql-docs-7.4.6.tar.gz and unzip it .I can`t intall i
PG version =
"PostgreSQL 8.0.1 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.2.3
(mingw special 20030504-1)"
Attached is the regression result of my test on Pg8.0.1 win32. The problem
is quite random. On the second round, it just disappeared.
first round --
I encounter the similar problem in "make check" (win2k-mingw, 8.0.1). The
regression test could randomly fail due to "could not write block (Invalid
argument)" problem or could not "remove file" problem.
Regards,
Qingqing
p.s. I believe this could be a potential serious problem, so I forward it t
46 matches
Mail list logo
