Re: [HACKERS] Windows 7, Visual Studio 2010: building PgAdmin3
zeray87 wrote: Hello guys, This is my first ever post and here goes my apology for being newbie. I have been able to build PgAdmin3 after several days of hassle on building PgAdmin3 using build-wxmsw.bat. If I remember it right for PgAdminIII needed mingw now. Thanks. -- Yury Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Html parsing and inline elements
On Wed, Apr 13, 2016 at 9:57 AM, Marcelo Zabani wrote: > Hi, Tom, > > You're right, I don't think one can argue that the default parser should > know HTML. > How about your suggestion of there being an HTML parser, is it feasible? I > ask this because I think that a lot of people store HTML documents these > days, and although there probably aren't lots of HTML with words written > along multiple inline elements, it would certainly be nice to have a proper > parser for these use cases. > > What do you think? > I recommend using Apache Tika [1] for plain text extraction from HTML. There are so many weird edge cases when parsing HTML that it is easier to use something that is already mature than reinventing the wheel. 1. https://tika.apache.org/ Thanks, Ryan Pedela
[HACKERS] About subxact and xact nesting level...
Still trying to find my way around the source code… The file xact.c contains references to sub-transactions (subxact) and transaction nesting level, but no obvious documentation about what these correspond to in SQL. A search shows that plpython supports something called “proper sub transactions”. There are random mentions of subtransactions in the release notes, but nothing substantive that I can find, and nothing about transaction nesting. Any pointers to docs or help to understand much appreciated. Regards David M Bennett FACS _ Andl - A New Database Language - andl.org
Re: [HACKERS] About subxact and xact nesting level...
On Mon, May 2, 2016 at 12:24 PM, wrote: > Still trying to find my way around the source code… > > > > The file xact.c contains references to sub-transactions (subxact) and > transaction nesting level, but no obvious documentation about what these > correspond to in SQL. A search shows that plpython supports something called > “proper sub transactions”. There are random mentions of subtransactions in > the release notes, but nothing substantive that I can find, and nothing > about transaction nesting. > > > > Any pointers to docs or help to understand much appreciated. Subtransactions are used to implement SAVEPOINT, and also BEGIN blocks with EXCEPTION clauses in plpgsql. http://www.postgresql.org/docs/9.5/static/sql-savepoint.html http://www.postgresql.org/docs/9.5/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING -- Thomas Munro http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] About subxact and xact nesting level...
Thomas Munro writes: > On Mon, May 2, 2016 at 12:24 PM, wrote: >> The file xact.c contains references to sub-transactions (subxact) and >> transaction nesting level, but no obvious documentation about what these >> correspond to in SQL. > Subtransactions are used to implement SAVEPOINT, and also BEGIN blocks > with EXCEPTION clauses in plpgsql. Yeah. The implementation is based on nested subtransactions, and that concept also applies pretty directly to, eg, BEGIN/EXCEPT blocks in plpgsql. But what's exposed to SQL is SAVEPOINT/RELEASE SAVEPOINT/ ROLLBACK TO SAVEPOINT, because those operations are what the standard specifies. If you hold your head at the correct angle you can see those as nested subtransactions, but it's not exactly obvious --- mainly because RELEASE and ROLLBACK can exit multiple levels of nested subtransaction in one command. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] snapshot too old, configured by time
On Sat, Apr 23, 2016 at 10:20:19AM -0400, Bruce Momjian wrote: > On Sat, Apr 23, 2016 at 12:48:08PM +0530, Amit Kapila wrote: > > On Sat, Apr 23, 2016 at 8:34 AM, Bruce Momjian wrote: > > > > > > I kind of agreed with Tom about just aborting transactions that held > > > snapshots for too long, and liked the idea this could be set per > > > session, but the idea that we abort only if a backend actually touches > > > the old data is very nice. I can see why the patch author worked hard > > > to do that. As I understand it, a transaction trying to access a shared buffer aborts if there was a cleanup on the page that removed rows it might be interested in. How does this handle cases where vacuum removes _pages_ from the table? Does vacuum avoid this when there are running transactions? > Also, it seems we have similar behavior already in applying WAL on the > standby --- we delay WAL replay when there is a long-running > transaction. Once the time expires, we apply the WAL. Do we cancel the > long-running transaction at that time, or wait for the long-running > transaction to touch some WAL we just applied? If the former, does > Kevin's new code allow us to do the later? Is this a TODO item? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
