Stack trace:
#0 0x0031a147c15c in memcpy () from /lib64/libc.so.6
#1 0x00450cb8 in __memcpy_ichk (tuple=0x7fffb29ac900) at
/usr/include/bits/string3.h:51
#2 heap_copytuple (tuple=0x7fffb29ac900) at heaptuple.c:592
#3 0x00543d4c in EvalPlanQualFetchRowMarks (epqstate=0x3cd8
Thanks Tom for your reply .
However, This is not a very long running query.
This was supposed to update only one row in a table.
Moreover, it cant be waiting for a lock as
other processes were able to update the same table at the same time.
restarting the process which was stuck because of this
Gordon Shannon writes:
> I'd love to send you a stack trace. Any suggestions on how to get one? It
> has since happened again, on the same update command, so I'm guessing I can
> repeat it.
http://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
I'd love to send you a stack trace. Any suggestions on how to get one? It
has since happened again, on the same update command, so I'm guessing I can
repeat it.
On Thu, Dec 30, 2010 at 6:52 PM, Tom Lane-2 [via PostgreSQL] <
ml-node+3323151-436577542-56...@n5.nabble.com
> wrote:
> Gordon Shannon
Gordon Shannon writes:
> Running Centos, just upgraded our production db from 8.4.4 to 9.0.2 last
> night. About 20 hours later, an update statement seg faulted and crashed
> the server. This is a typical update that has worked fine for a long time.
Could we see a stack trace from that? Or at l
On 31/12/2010, at 12:43 AM, Carlos Mennens wrote:
> On Mon, Dec 20, 2010 at 7:26 PM, Thom Brown wrote:
>> I know this topic has gone quiet, I still think it's worth investing
>> time and resources in. I don't expect any progress to be made until
>> the new year now, but I hope we can continue t
Sorry folks, this is an old message I forgot to copy pgsql-general on.
Begin forwarded message:
> From: Elliot Chance
> Date: 21 December 2010 11:48:07 AM AEDT
> To: Thom Brown
> Subject: Re: [GENERAL] Postgres forums ... take 2
>
> On 21/12/2010, at 11:26 AM, Thom Brown wrote:
>
>> On 29 Nov
Hi,
Running Centos, just upgraded our production db from 8.4.4 to 9.0.2 last
night. About 20 hours later, an update statement seg faulted and crashed
the server. This is a typical update that has worked fine for a long time.
20898 datafeed (58628) 2010-12-30 19:28:14 EST [103]LOG: process 2089
On 12/30/10 6:39 AM, prabakaran.a wrote:
Dear All,
We are using Postgresql 9.0.1(binary) in our Java Application.
In some windows xp sp3 machines, we found that the executable files
related to postgresql are not working. while executing those files(ex:
initdb.exe), following error thrown in c
Dear All,We are using Postgresql 9.0.1(binary) in our Java Application.In some windows xp sp3 machines, we found that the executable files related to postgresql are not working. while executing those files(ex: initdb.exe), following error thrown in console "The system cannot execute the specified p
gvi...@gmail.com (gvim) writes:
> I'm putting together a database for a web project which has a lot of
> HR components which I imagine are fairly standardised so, to avoid
> re-inventing the wheel, is there a source of standard, downloadable
> schemas for common projects?
One might imagine so...
gvi...@gmail.com (gvim) writes:
> If a table representing contact details can have 2 but no more than 2 email
> addresses is it really worth factoring-out email addresses to a separate
> table. Technically it's a 1-to-many relationship so should be done this way
> but what is the general practic
"tamanna madaan" writes:
> I am using postgres-8.1.2 and have been using psqlodbc-08.03.0200 driver to
> connect
> to the databse. One of the queries I executed from my appilcation have got
> stuck for an
> indefinite amount of time causing my application to hang.
Are you sure you didn't simpl
On 30/12/2010 10:28, tamanna madaan wrote:
Hi All
I am using postgres-8.1.2 and have been using psqlodbc-08.03.0200 driver to
connect
I'd imagine you're going to get a *flood* of responses saying this, but
here goes anyway - the version of Postgres you're using is VERY old, and
missing 21 s
Hi All
I am using postgres-8.1.2 and have been using psqlodbc-08.03.0200 driver to
connect
to the databse. One of the queries I executed from my appilcation have got
stuck for an
indefinite amount of time causing my application to hang. So I cored the
application. The
core file gives a backtr
On Wed, Dec 29, 2010 at 11:20 PM, Adarsh Sharma
wrote:
> Dear all,
>
> I am working on some common tasks that need to be performed on regular
> intervals in a large Database Servers. I find below lists of tasks that need
> to be performed and Please tell me if i missed some.
>
> 1. Tacking Daily,
On Thu, Dec 30, 2010 at 06:02:54PM +0100, Vincent Veyron wrote:
>
> I'm partial to Emacs, but I'm surprised nobody mentionned Abiword :
>
> http://www.abisource.com/
I think Abiword would be a very bad editor for any kind of database
work, no? It's intended as a word processor rather than a tex
Le mercredi 29 décembre 2010 à 11:09 -0800, Tim Bruce - Postgres a
écrit :
> On Wed, December 29, 2010 10:59, John R Pierce wrote:
> I'd also like to throw in Context for Windows as an Editor. It's also
> free and has syntax highlighting for almost everything imaginable (on
> Windows and *ix).
Carlos Mennens writes:
> I've been reading the documentation and I'm trying to understand what
> 'GRANT' options make up a 'superuser' in PostgreSQL.
Superuser-ness is not a grantable privilege; it's an attribute of a
role. See CREATE/ALTER ROLE.
> Obviously 'Carlos' is a superuser but what doe
I've been reading the documentation and I'm trying to understand what
'GRANT' options make up a 'superuser' in PostgreSQL.
I've got my account which is 'carlos' and then I have an account
called 'jason'. Can someone please explain the difference between the
two roles:
postgres=# \dg
L
Hello.
I use Postgres 8.4.5 via perl DBI.
And i try to use cursors WITH HOLD to materialize
often used queries.
My question is how many cursors may be
declared per session and which memory setting s
to adjust for them ?
regards.
pasman
--
Sent via pgsql-general mailing list (pgsq
On Thu, Dec 30, 2010 at 7:30 AM, gvim wrote:
> I want a user to be able to INSERT new rows but not UPDATE or
> DELETE rows ...
This part is easily done:
http://www.postgresql.org/docs/9.0/interactive/sql-grant.html
http://www.postgresql.org/docs/9.0/interactive/sql-revoke.html
http://www.postgres
On 30 December 2010 16:30, gvim wrote:
> Is it possible, with PostgreSQL 9.0, to restrict access to specific table
> rows by `id`? I want a user to be able to INSERT new rows but not UPDATE or
> DELETE rows with `id` < 1616.
>
> gvim
>
>
I think the simplest way would be creating a trigger in whi
Is it possible, with PostgreSQL 9.0, to restrict access to specific table rows by
`id`? I want a user to be able to INSERT new rows but not UPDATE or DELETE rows
with `id` < 1616.
gvim
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
h
On Mon, Dec 20, 2010 at 7:26 PM, Thom Brown wrote:
> I know this topic has gone quiet, I still think it's worth investing
> time and resources in. I don't expect any progress to be made until
> the new year now, but I hope we can continue this after the Christmas
> period is over.
>
> And nice wo
25 matches
Mail list logo
