Hi all,
Inspired by the awesome work done by Oleg sir in HStore, I have been thinking
about making a graph data type as an extension in postgres.
I have been reading about graph databases and how storing data in graphs can
lead to some really awesome functionalities such as social network analy
Dimitri Fontaine writes:
> Tom Lane writes:
>> Yeah, I was just looking at the IfSupported variant. In the structure
>> I just suggested (separate ProcessSlowUtility function), we could make
>> that work by having switch cases for some statements in both functions,
> I've done it the way you pr
The pg_resetxlog -m option was changed from
-m XID set next multitransaction ID
to
-m XID,OLDESTset next multitransaction ID and oldest value
but the man page does not reflect that change.
It was introduced in 0ac5ad5134f2769ccbaefec73844f8504c4d6182 "Improve
concurrency of f
Bruce,
So here's my draft list of "Major Enhancements" for the relase notes:
* Writeable Foreign Tables
* pgsql_fdw driver for federation of PostgreSQL databases
* Automatically updatable VIEWs
* MATERIALIZED VIEW declaration
* LATERAL JOINs
* Additional JSON constructor and extractor functions
*
Dimitri Fontaine writes:
> Tom Lane writes:
>> Yeah, I was just looking at the IfSupported variant. In the structure
>> I just suggested (separate ProcessSlowUtility function), we could make
>> that work by having switch cases for some statements in both functions,
> I've done it the way you pr
On 27 April 2013 20:12, Robert Haas wrote:
> My feeling is that it would be better not to back-patch this, but just
> fix it in master. Given the present uses of COPY-BOTH mode, the
> problems seem to be limited to bad error messages, so it's arguably
> not a critical bug fix. Also, I think tha
Will Childs-Klein writes:
> I've been doing some extensive modifications of the storage manager (md.c)
> in postgres. My code all compiles just fine, but when i run initdb, i
> receive the following output:
> "creating template1 database in /home/accts/wdc22/pgdata/base/1 ... ok
> initializing pg
Hello All,
I've been doing some extensive modifications of the storage manager (md.c)
in postgres. My code all compiles just fine, but when i run initdb, i
receive the following output:
"creating template1 database in /home/accts/wdc22/pgdata/base/1 ... ok
initializing pg_authid ... WARNING: no r
Robert Haas writes:
> On Sat, Apr 27, 2013 at 3:33 PM, Tom Lane wrote:
>> Um, wait, it's *not* in pg_class now, and what I was about to do was
>> go put it there. Is there a typo in the above para, or are you saying
>> you don't like either approach? If the latter, what concept have you
>> got
On Sat, Apr 27, 2013 at 3:33 PM, Tom Lane wrote:
>>> 1. The matviews mess. Changing that will force initdb, more than
>>> likely, so we need it resolved before beta1.
>
>> I would like to rip out the whole notion of whether a materialized
>> view is scannable and am happy to do that on Monday if
Robert Haas writes:
> On Sat, Apr 27, 2013 at 10:59 AM, Tom Lane wrote:
>> Of the items on the 9.3 open-items page,
>> https://wiki.postgresql.org/wiki/PostgreSQL_9.3_Open_Items
>> there are at least three that seem like absolute drop-dead stop-ship issues:
> I completely agree. I think it's co
On Sat, Apr 27, 2013 at 10:59 AM, Tom Lane wrote:
> The schedule says we're going to wrap 9.3beta1 on Monday, but it doesn't
> feel to me like we are anywhere near ready to ship a credible beta.
> Of the items on the 9.3 open-items page,
> https://wiki.postgresql.org/wiki/PostgreSQL_9.3_Open_Items
On Sat, Apr 27, 2013 at 6:02 AM, Simon Riggs wrote:
> On 27 April 2013 03:22, Robert Haas wrote:
>> It seems the backend and libpq don't agree. The backend makes no
>> special provision to wait for a CopyDone message if an error occurs
>> during copy-both. It simply sends an ErrorResponse and t
Jeff Janes writes:
> After 87306184580c9c49717, if the postmaster dies without cleaning up (i.e.
> power outage), running "pg_ctl start" just gives this message and then
> exits:
> pg_ctl: another server might be running
> Under the old behavior, it would try to start the server anyway, and
> su
Noah Misch writes:
> On Sat, Apr 27, 2013 at 10:59:32AM -0400, Tom Lane wrote:
>> As far as #1 goes, I think we have little choice at this point but to
>> remove the unlogged-matviews feature for 9.3.
> This perspective is all wrong. I hate to be blunt, but that thread ended with
> your technica
On Sat, Apr 27, 2013 at 10:59:32AM -0400, Tom Lane wrote:
> The schedule says we're going to wrap 9.3beta1 on Monday, but it doesn't
> feel to me like we are anywhere near ready to ship a credible beta.
> Of the items on the 9.3 open-items page,
> https://wiki.postgresql.org/wiki/PostgreSQL_9.3_Ope
Simon Riggs writes:
> libpq updates are much harder to roll out, so it would be better to
> assume that it is correct and the backend is wrong if we want to
> backpatch the fix.
I don't think that's a particularly sound argument.
If we view this as a protocol definitional issue, which it is, the
The schedule says we're going to wrap 9.3beta1 on Monday, but it doesn't
feel to me like we are anywhere near ready to ship a credible beta.
Of the items on the 9.3 open-items page,
https://wiki.postgresql.org/wiki/PostgreSQL_9.3_Open_Items
there are at least three that seem like absolute drop-dead
On 27 April 2013 03:22, Robert Haas wrote:
> It seems the backend and libpq don't agree. The backend makes no
> special provision to wait for a CopyDone message if an error occurs
> during copy-both. It simply sends an ErrorResponse and that's it.
> libpq, on the other hand, treats either CopyD
19 matches
Mail list logo
