On Fri, Jul 26, 2013 at 7:28 PM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8336
> Logged by: Harsh Vardhan Upadhyay
> Email address: harshmailbo...@gmail.com
> PostgreSQL version: 9.2.2
> Operating system: windows
> Description:
>
> Dear Si
Hi,
I would like to consult with you a problematic response put by PostgreSQL after
transaction recovery run by Narayana (JBossTS).
I work on tests for Narayana and I hit a issue with PostgreSQL. The db returns
incorrect code XAException.XA_HEURHAZ when the TM does recovery after crash of
the
Ondrej Chaloupka writes:
> The OTS specification requires both bottom up and top down recovery to be
> triggered by the recovering resource. This causes that two rollback calls are
> done against the DB. DB receives rollback call and does the rollback. Then
> for the second time it returns the
Tom Jenkinson writes:
> A little bit of information in the linked bugzilla report is that the
> exception being returned has an XA error code of XAER_RMERR "An error
> occurred in rolling back the transaction branch. The resource manager is
> free to forget about the branch when returning this
Tom Jenkinson writes:
> On Mon 29 Jul 2013 15:46:12 BST, Tom Lane wrote:
>> No idea, but in any case that's outside Postgres' purview. It's barely
>> possible that the Postgres JDBC driver has something to do with that,
>> but it sounds more like the XA manager's turf.
> I am not sure what you m
Hi,
Attached is a psql .crash file related to the problem reported in BUG 8343.
Thanks,
Charles Sheridan
Process: postgres [2831]
Path:/Library/PostgreSQL/9.2/bin/postgres
Identifier: postgres
Version: ???
Code Type: X86-64 (Native)
Parent Process: post
Hi Tom,
On Mon 29 Jul 2013 15:46:12 BST, Tom Lane wrote:
Tom Jenkinson writes:
A little bit of information in the linked bugzilla report is that the
exception being returned has an XA error code of XAER_RMERR "An error
occurred in rolling back the transaction branch. The resource manager is
fr
The following bug has been logged on the website:
Bug reference: 8344
Logged by: philip
Email address: luc...@gmail.com
PostgreSQL version: 9.2.4
Operating system: OSX 10.8
Description:
Executing,
CREATE EXTENSION plpythonu;
** Error **
ERROR: could no
Dear Sir/Mam,
I have migrated my database from SQL Server to PosgreSQL.
All functionality is working fine, but pgAgent is not working.
Jobs are creating, but not running.
As i have downladed and installed pgAgent, but can't able to regsister its
service(postgreSQL Scheduling Agent-pgAgent ) in ser
Hello again
Bug can't be reproduced any more
Consider it closed.
Thanks,
Euclid
From: Pavan Deolasee [mailto:pavan.deola...@gmail.com]
Sent: Thursday, July 25, 2013 8:53 PM
To: euc...@yandex-team.ru
Cc: Pg Bugs
Subject: Re: [BUGS] BUG #8334: Merge Join drops records
On Thu, Ju
Hi Tom,
A little bit of information in the linked bugzilla report is that the
exception being returned has an XA error code of XAER_RMERR "An error
occurred in rolling back the transaction branch. The resource manager is
free to forget about the branch when returning this error so long as all
Hello,
I have noticed that when I execute this query, the DB (postgresql) is
crashed.
select
trunc(st_area(ST_MakeValid(st_GeometryFromText(st_astext('01030001000D002659559057004241C8275DD4EC815241F8F059C15F004241FC4DCD26F1815241544B80CB6500424163EB5BACEF81524156457A656B004241B9FF0442E
On Wed, Jul 24, 2013 at 5:18 AM, Willy-Bas Loos wrote:
> Hi,
>
> The manual says:
> It is recommended that you use the pg_dump and pg_dumpall programs from the
> newer version of PostgreSQL, to take advantage of enhancements that might
> have been made in these programs. Current releases of the du
On Jul 29, 2013, at 16:57, Tom Jenkinson wrote:
> Hi Tom,
>
> On Mon 29 Jul 2013 15:46:12 BST, Tom Lane wrote:
>> Tom Jenkinson writes:
>>> A little bit of information in the linked bugzilla report is that the
>>> exception being returned has an XA error code of XAER_RMERR "An error
>>> occurre
On Mon, Jul 29, 2013 at 4:11 AM, matty wrote:
> Hello,
> I have noticed that when I execute this query, the DB (postgresql) is
> crashed.
>
I executed this query without problem. This are the versions i have, i
will recommend you to upgrade those that differ from yours and retry
(specially geos,
Dear Pavel and Andrew,
avoiding the nulls solves the thing - thank you! I was considering NULL
as 0... lame.
I just wonder why it was working in the console, but it is not important
- at the moment it works just fine.
Cheers,
Petr
On 27.7.2013 22:59, Pavel Stehule wrote:
Hello
2013/7/27 An
Hi list!
depressed me gets error messages like these:
2013-07-29 20:57:09 UTC ERROR: could not access
status of transaction 8393477
2013-07-29 20:57:09 UTC DETAIL: Could not open
file "pg_clog/0008": No such file or directory.
combined with the error output of queries that do not work.
I l
On Mon, Jul 29, 2013 at 10:19 PM, Klaus Ita wrote:
> My feeling is, that 'something' got confused with hot-standby and
> wal_archiving leading to this situation, that seems to be partially xfs
> caused?? xfs_repair mentionned some missing files, that pg did not
> expect to have (maybe truncate
Hi Greg!
Thank you for your immediate response. I cannot tell you the xfs_repair
files that were mangled but I did the repair on an lvm snapshot. the files
were not listed in 'select * from pg_class'. Might not be THE source for
inodes needed by the cluster?
I agree, it does not really sonud like
19 matches
Mail list logo
