[BUGS] BUG #8364: BUG: Patch for fail-back without fresh backup

[digoal]

The following bug has been logged on the website:

Bug reference:  8364
Logged by:  digoal.zhou
Email address:  dig...@126.com
PostgreSQL version: Unsupported/Unknown
Operating system:   CentOS 5.8 x64
Description:

When i use failback_safe_standby_v4.patch patch the postgresql 9.4 devel
http://git.postgresql.org/gitweb/?p=postgresql.git;a=snapshot;h=e5592c61adb0766eaee53ec07d2f05783d1c6548;sf=tgz
.patch success. but test in async replicatoin environment fail-back not
success.
detail below:
1. primary config
wal_level = hot_standby
synchronous_commit = remote_write
synchronous_transfer=data_flush # or all, but fail-back also not success.
2. standby config


3. test sql
digoal=# create table test (id int primary key, info text, crt_time
timestamp);
CREATE TABLE
digoal=# create or replace function func() returns void as $$
digoal$# declare 
digoal$#   v_id int;
digoal$# begin
digoal$#   v_id := round(500*random());
digoal$#   update test set
info=md5(random()::text),crt_time=clock_timestamp() where id=v_id;
digoal$#   if found then
digoal$# return;
digoal$#   else
digoal$# insert into test values
(v_id,md5(random()::text),clock_timestamp());
digoal$#   end if;
digoal$#   return;
digoal$# end;
digoal$# $$ language plpgsql strict;
CREATE FUNCTION
4. pgbench running
pgbench -M prepared -f ./test.sql -r -n -h $PGDATA -p 2999 -U postgres -c 16
-j 4 -T 100 digoal
5. checkpoint on master success


6. shutdown or promote standby
success
7. pgbench stop


8. shutdown master, and fail-back to standby, but not success.
log below.
2013-08-06 09:39:53.650 CST,,,13339,,520053e9.341b,2,,2013-08-06 09:39:53
CST,,0,FATAL,XX000,"could not receive data from WAL stream: ERROR: 
requested starting point 0/5200 is ahead of the WAL flush position of
this server 0/45AD6088
""libpqrcv_receive, libpqwalreceiver.c:513",""


# ### but i can success fail-back when use sync replication and this patch.
detail info at my blog: 
http://blog.163.com/digoal@126/blog/static/16387704020137551911457
 



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #8362: postres webserver

[Greg Stark]

On Sun, Aug 4, 2013 at 10:03 AM,   wrote:
> Not really a bug but a?

Questions can be sent to pgsql-gene...@postgresql.org

> I have been using you enterprisedb

Then you should contact enterprisedb for support or use their forums.

> It install easy with XAMPP but I can not get it to load with yours.

Whoever you contact you will need to provide them with details of what
happens. They're not going to be able to guess why it's not working.

-- 
greg


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #8362: postres webserver

[Ashesh Vashi]

Please contact EnterpriseDB related to this.
Please visit the following url for that:
http://forums.enterprisedb.com/forums/show/12.page

This is neither a PostgreSQL's bug, or related to it.

On Sun, Aug 4, 2013 at 2:33 PM,  wrote:

> The following bug has been logged on the website:
>
> Bug reference:  8362
> Logged by:  Keith Sargent
> Email address:  kd_sarg...@msn.com
> PostgreSQL version: 9.2.2
> Operating system:   win7
> Description:
>
> Not really a bug but a? I have been using you enterprisedb apachephp local
> web server to develop
> was hoping to install phalcon c# extension. It install easy with XAMPP but
> I
> can not get it to load with yours.  I add the extension with and without a
> direct link,I put the php_phalcon.dll in different directories. I'm
> guessing
> it's a phalcon issue you use a MSVC10 for the compiler and xampp uses a
> MSVC9 and phalcon is also compiled in MSVC9.  I do not know if this will be
> an Issues on my web-server, but I would like to start developing on my
> local
> server and I think i would be a very nice feature set for you guys to
> offer.
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>



-- 
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company



*http://www.linkedin.com/in/asheshvashi*

Re: [BUGS] BUG #8362: postres webserver

[Christopher Browne]

There are several things confusing here that seem to indicate that
this is not a bug...

1.  Postgres is not a web server.  It is a database management system,
and thus extensions one might hope to add to a web server are not
logical to expect to connect to Postgres.

2.  It sounds as though you are using a version of Postgres that has
been customized by EnterpriseDB, and, as that is not something that
the community has code for, we're not able to be of much assistance.
As a user of EnterpriseDB's products, you are presumably a customer,
and should expect to get customer support from them.  Most pointedly,
their build procedures are theirs, and not ours, and that's a place
where any help relevant to you would really need to come from
EnterpriseDB.


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [JDBC] [BUGS] Incorrect response code after XA recovery

[Jeremy Whiting]

Hello Tom,
 A quick update on progress. A second PR was created to provide a patch.

https://github.com/pgjdbc/pgjdbc/pull/76

Regards,
Jeremy

On 31/07/13 12:36, Jeremy Whiting wrote:

Hi Tom,
  The driver currently doesn't report back to the calling client (tm)
XAException.XAER_NOTA code as Ondrej and Tom Jenkinson have identified.
Instead it returns XAException.XAER_RMERR. See line 416

https://github.com/pgjdbc/pgjdbc/blob/master/org/postgresql/xa/PGXAConnection.java#416

  which imo is used for general errors in the resource manager.

  I've written a test case that can be pulled into the pgjdbc testsuite
that will make verifying this error easier. It is based on the example
code Tom Jenkinson provided. A pull request has been created which can
be found here...

https://github.com/pgjdbc/pgjdbc/pull/73

  I am currently coding up a change to the driver in anticipation there
is agreement in the pgjdbc group to change the rollback method. Another
pull request will be created for that. Let's see what discussion and
decision is made by the more active members in pgjdbc.

Regards,
Jeremy

On 29/07/13 16:11, Tom Lane wrote:

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 mean here as I don't know the structure of how
the PostGres project is packaged, all I know is that the PostGres JDBC
driver component appears to be returning an XAException with the
message "Error rolling back prepared transaction" and an errorCode of
XAException.XAER_RMERR rather than XAER_NOTA.
Is there a different component within your bug tracking system  we
should be using to raise this against the JDBC driver instead?

The folk who would fix anything in the JDBC driver tend to read
pgsql-jdbc sooner than pgsql-bugs, so cc'ing there for comment.

regards, tom lane







--
Jeremy Whiting
Senior Software Engineer, Performance Team
Red Hat


Registered Address: Red Hat UK Ltd, 64 Baker Street, 4th Floor, London. W1U 
7DF. United Kingdom.
Registered in England and Wales under Company Registration No. 03798903. 
Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson (USA), 
Charlie Peters (USA)



--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #8355: PL/Python 3 can't convert infinity to PostgreSQL's value

[Basil Peace]

I based on the documentation of PostgreSQL  
(http://www.postgresql.org/docs/9.2/static/datatype-numeric.html#DATATYPE-FLOAT)
 which says about 'Infinity' and '-Infinity' and doesn't mention other possible 
spellings, including 'inf'.
And on my installation of 9.2.4 'inf' doesn't work too (as I supposed according 
to documentation):

SELECT 'inf'::float8

ERROR:  invalid input syntax for type double precision: "inf"
LINE 2: SELECT 'inf'::float8

According to Python's documentation 
(http://docs.python.org/2/library/stdtypes.html#typesnumeric), handle of 
infinities and NaNs was added in 2.6. At least this works in 2.7.1:

Python 2.7.1 (r271:86832, Apr  1 2013, 01:27:27) [MSC v.1600 64 bit 
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>  float('inf')
inf
>>>  float('infinity')
inf
>>>  float('+inf')
inf
>>>  float('-inf')
-inf

So, Python is honest in this way. And, C99 says that style of representation 
('inf' or 'infinity') is implementation-defined, so it is all OK with modern 
Python.

>  We already backstop strtod() for these cases:
>
>  NaN
>  Infinity
>  -Infinity
>
>  but the wording of the spec clearly requires +Infinity as well as the
>  forms with just "inf".  (It also appears to require +/- NaN to be
>  accepted, but I have no idea what that would mean and suspect it to
>  be a thinko.)

As I can judge, signed NaNs are from the same world as signed zeros and signed 
infinities. Strictly speaking: (-0)/(+0) is -NaN, (-inf)/(+inf) is -NaN, and so 
on.
I think that PostgreSQL's ability to handle signed zeros (and all other rare 
stuff) depends on compiler used. Google says me that '-NaN' exists in modern 
glibc. I don't know about MSVC. My Python accepts '-nan' as input, but doesn't 
give me '-NaN' as output.
So, I think it would be good if '-NaN' and other forms were workable.

-- 
Best regards,
Basil Peace


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8362: postres webserver

[kd_sargent]

The following bug has been logged on the website:

Bug reference:  8362
Logged by:  Keith Sargent
Email address:  kd_sarg...@msn.com
PostgreSQL version: 9.2.2
Operating system:   win7
Description:

Not really a bug but a? I have been using you enterprisedb apachephp local
web server to develop
was hoping to install phalcon c# extension. It install easy with XAMPP but I
can not get it to load with yours.  I add the extension with and without a
direct link,I put the php_phalcon.dll in different directories. I'm guessing
it's a phalcon issue you use a MSVC10 for the compiler and xampp uses a
MSVC9 and phalcon is also compiled in MSVC9.  I do not know if this will be
an Issues on my web-server, but I would like to start developing on my local
server and I think i would be a very nice feature set for you guys to offer.



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] BUG #8363: checksum verification fails with StackBuilder

[mnl . post]

The following bug has been logged on the website:

Bug reference:  8363
Logged by:  Manuel
Email address:  mnl.p...@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system:   windows 8 x64 
Description:

With latest postgreSQL download for windows x64 (9.3 beta 2): 
on windows 8 x64, checksum verification fails with Application StackBuilder
when downloading any drivers (odbc etc.).




-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs