Alvaro Herrera wrote:
Josh Berkus escribió:
And snaphsots have more compile dependancies than releases do.
As far as I know, a snapshot is identical to a release in that regard.
If they are not, that's a bug and we can fix it before weekend.
yeah - snapshots do have the same compile time
Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
On 3/29/10 7:46 AM, Joachim Wieland wrote:
I actually assume that whenever people are interested
in a very fast dump, it is because they are doing some maintenance
task (like migrating to a different server) that involves pg_dump. In
these
To whom may concern,
My name is Zhai Boxuan, a student from China.
I am now a Master Student of National University of Singapore. And, before I
came to Singapore, I have got another master degree in Wuhan University. In
that period, I focus mainly on implementing a novel Object-oriented database
On 30 March 2010 08:26, Zhai Boxuan bxz...@gmail.com wrote:
I have read some infor about the MERGE command, which has not been
implemented yet in Postgres 8. I considered the problem and have a brief plan
for the jobs.
You may find these to be some help if you haven't already read them:
Hi,
The attached patch improves the documents about SR as follows:
* Improve the description about the setup procedure of SR.
o Add the link to the recovery.conf parameter if needed.
o Add the example of recovery.conf setting.
* Document what should be monitored for avoiding the disk full
On Mon, Feb 1, 2010 at 11:49 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Sat, Jan 30, 2010 at 12:54 PM, Fujii Masao masao.fu...@gmail.com wrote:
HOWEVER, I do believe this is an issue we could live with for 9.0 if
it's going to lead to a whole lot of additional debugging of SR. But if
On Wed, Mar 3, 2010 at 11:03 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Mar 2, 2010 at 10:52 PM, Fujii Masao masao.fu...@gmail.com wrote:
It's not clear what it should return, a TLI corresponding the filename
of the WAL segment the record was replayed from, so that you can use
On Tue, Jun 17, 2008 at 11:17 AM, Hiroshi Saito
z-saito(at)guitar(dot)ocn(dot)ne(dot)jp wrote:
Hi.
Please this.
http://winpg.jp/~saito/pg_work/OSSP_win32/msvc/
Ahh, a makefile - that makes things somewhat clearer :-)
Thanks - I've updated the build machine so future releases will
include
On tis, 2010-03-30 at 08:39 +0200, Stefan Kaltenbrunner wrote:
on fast systems pg_dump is completely CPU bottlenecked
Might be useful to profile why that is. I don't think pg_dump has
historically been developed with CPU efficiency in mind.
--
Sent via pgsql-hackers mailing list
On mån, 2010-03-29 at 17:03 -0700, Josh Berkus wrote:
The idea crudely is the following:
I want to implement a image database system: This will have the
following quality:
This seems fine, but I believe it's been done before. You might want to
search for existing projects, and make
On Tue, 30 Mar 2010 13:01:54 +0200, Peter Eisentraut pete...@gmx.net
wrote:
On tis, 2010-03-30 at 08:39 +0200, Stefan Kaltenbrunner wrote:
on fast systems pg_dump is completely CPU bottlenecked
Might be useful to profile why that is. I don't think pg_dump has
historically been developed
Peter Eisentraut wrote:
On tis, 2010-03-30 at 08:39 +0200, Stefan Kaltenbrunner wrote:
on fast systems pg_dump is completely CPU bottlenecked
Might be useful to profile why that is. I don't think pg_dump has
historically been developed with CPU efficiency in mind.
It's not pg_dump that is
Some recent off-list discussion has suggested that we should keep
plperl's copy of ppport.h in sync on all branches, just as we do with
timezone data files. So when we update it on HEAD we should
simultaneously update the back branches. It's a derived file, produced
by the perl module
On Tue, Mar 30, 2010 at 1:37 AM, Takahiro Itagaki
itagaki.takah...@oss.ntt.co.jp wrote:
Hi, I have some questions about 9.0 release note.
I'd like to work for some of them if required. Comments welcome.
* Allow per-tablespace sequential and random page cost variables
As Jeff Davis pointed out, I followed the modification he suggested and
now I want to have a basic matching only. I think atleast the
fingerprint processing can be done in summer (if not the image
processing). Is it a good GSoC project now?
Waiting for a reply eagerly
Thanks and regards,
As Jeff Davis pointed out, I followed the modification he suggested and
now I want to have a basic matching only. I think atleast the
fingerprint processing can be done in summer (if not the image
processing). Is it a good GSoC project now?
Waiting for a reply eagerly
Thanks and regards,
Hello,
I was noticed on little bit strange feature of PostgreSQL 8.4 and 9.0
we can use a non existing column name. What does mean?
postgres=# create table h(a int, b int);
CREATE TABLE
Time: 2,604 ms
postgres=# insert into h values(199,22);
INSERT 0 1
Time: 0,970 ms
postgres=# explain verbose
Also, where are we on using full names rather than first names only? I
don't see the point in omitting the last names. Are we trying to
obscure to outsiders who is really working on our code?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company
On Tue, Mar 30, 2010 at 12:56 AM, Anindya Jyoti Roy anind...@iitk.ac.in wrote:
As Jeff Davis pointed out, I followed the modification he suggested and now
I want to have a basic matching only. I think atleast the fingerprint
processing can be done in summer (if not the image processing). Is it
MUHAMMAD ASIF anaeem...@hotmail.com writes:
I have downloaded uuid-1.6.2.tar.gz from http://www.ossp.org/pkg/lib/uuid/ .
It successfully built with MinGW gcc and made libuuid.a, I renamed it to
uuid.lib to build uuid-ossp contrib module with visual studio 2005. uuid-ossp
give the following
2010/3/30 Pavel Stehule pavel.steh...@gmail.com:
Hello,
I was noticed on little bit strange feature of PostgreSQL 8.4 and 9.0
we can use a non existing column name. What does mean?
postgres=# create table h(a int, b int);
CREATE TABLE
Time: 2,604 ms
postgres=# insert into h
Ian Barwick barw...@gmail.com writes:
2010/3/30 Pavel Stehule pavel.steh...@gmail.com:
we can use a non existing column name. What does mean?
FYI this has caused me (and presumably a few other people) a bit of
head-scratching, e.g.:
2010/3/30 Tom Lane t...@sss.pgh.pa.us:
Ian Barwick barw...@gmail.com writes:
2010/3/30 Pavel Stehule pavel.steh...@gmail.com:
we can use a non existing column name. What does mean?
FYI this has caused me (and presumably a few other people) a bit of
head-scratching, e.g.:
Robert Haas robertmh...@gmail.com writes:
On Tue, Mar 30, 2010 at 12:56 AM, Anindya Jyoti Roy anind...@iitk.ac.in
wrote:
As Jeff Davis pointed out, I followed the modification he suggested and now
I want to have a basic matching only. I think atleast the fingerprint
processing can be done
The interpretation of the standard in the above way (DECLARE is declarative,
...
It's not just interpretation, but also a regression if we were to change this.
The uniqueness problem can only be solved with modifying
the runtime library to keep track of the cursor names in the client.
It
Marc Cousins pointed out here
http://archives.postgresql.org/pgsql-general/2010-03/msg01123.php
that the constraint_exclusion = partition feature added in 8.4
does not do what you'd expect for the target relation of an UPDATE
or DELETE. That's because expansion of an inheritance set is managed
Fujii Masao wrote:
* Small code changes to handling of failedSources, inspired by your
comment. No change in functionality.
This is also available in my git repository at
git://git.postgresql.org/git/users/heikki/postgres.git, branch xlogchanges
I looked the patch and was not able to find
Tom Lane wrote:
Marc Cousins pointed out here
http://archives.postgresql.org/pgsql-general/2010-03/msg01123.php
that the constraint_exclusion = partition feature added in 8.4
does not do what you'd expect for the target relation of an UPDATE
or DELETE. That's because expansion of an
Hi MUHAMMAD-san.
Sorry late reaction...
unfortunately, My machine crashed and was not revitalized.:-(
However, There is a thing of now a few.
http://winpg.jp/~saito/pg_work/OSSP_win32/msvc/
I have a comment from Ralf S. Engelschall.
==
Sorry for being late with the release of OSSP uuid 2.0.0.
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Seems OK to me. It's worth noting though that if a module does do
palloc+memcpy of PlannerInfo, and it's compiled against the new sources
with the extra field, but used on an old server version, it will
memcpy() from beyond the end
On 3/29/10 5:04 PM, Magnus Hagander wrote:
Last i heard from Dave on that topic is that there's no chance of that
happening that quickly. He's on a plane now but I'm sure he'll confirm
that when he lands.
That means that we'll be doing the test-fest using Alpha4, materially.
Which is annoying
On Tue, Mar 30, 2010 at 4:43 PM, Josh Berkus j...@agliodbs.com wrote:
On 3/29/10 5:04 PM, Magnus Hagander wrote:
Last i heard from Dave on that topic is that there's no chance of that
happening that quickly. He's on a plane now but I'm sure he'll confirm
that when he lands.
That means that
joeyadams3.14...@gmail.com (Joseph Adams) writes:
I introduced myself in the thread Proposal: access control jails (and
introduction as aspiring GSoC student), and we discussed jails and
session-local variables. But, as Robert Haas suggested, implementing
variable support in the backend would
On Tue, Mar 30, 2010 at 9:36 AM, Dimitri Fontaine
dfonta...@hi-media.com wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Mar 30, 2010 at 12:56 AM, Anindya Jyoti Roy anind...@iitk.ac.in
wrote:
As Jeff Davis pointed out, I followed the modification he suggested and now
I want to have
On Tue, Mar 30, 2010 at 5:09 AM, Fujii Masao masao.fu...@gmail.com wrote:
I rebased the patch to HEAD. Is the patch still required for 9.0?
If not, I'd remove the open item of the smart shutdown during
recovery.
I am by no means an expert on this area of the code, but in the
interest of moving
I'd think that you could get quite a long ways on this, at least doing
something like dbslayer without *necessarily* needing to do terribly
much work inside the DB engine.
There's actually an HTTP framework tool for Postgres which already does
something of the sort. It was introduced at
On Tue, Mar 30, 2010 at 8:58 PM, Josh Berkus j...@agliodbs.com wrote:
I'd think that you could get quite a long ways on this, at least doing
something like dbslayer without *necessarily* needing to do terribly
much work inside the DB engine.
There's actually an HTTP framework tool for
On Wed, Mar 31, 2010 at 9:47 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 30, 2010 at 5:09 AM, Fujii Masao masao.fu...@gmail.com wrote:
I rebased the patch to HEAD. Is the patch still required for 9.0?
If not, I'd remove the open item of the smart shutdown during
recovery.
I am
Robert Haas wrote:
While it might be interesting to have/find/write a tool that puts an
HTTP/JSON layer around the DB connection, it's pretty much entirely
unrelated to the proposed project of creating a json type with
PostgreSQL analagous to the xml type we already have, which is what
the OP
On Wed, Mar 31, 2010 at 1:28 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Fujii Masao wrote:
* Small code changes to handling of failedSources, inspired by your
comment. No change in functionality.
This is also available in my git repository at
On Wed, Mar 31, 2010 at 7:01 AM, Robert Haas robertmh...@gmail.com wrote:
At the risk of being blunt, AFAICT, the delay in getting to beta has
little or nothing to do with testing and everything to do with the
fact that streaming replication got committed with a long list of open
items two
I discovered tonight that if you shut down a server, create
recovery.conf with standby_mode = 'on', and start it back up again,
you get this:
LOG: database system was shut down at 2010-03-30 22:34:09 EDT
LOG: entering standby mode
FATAL: recovery connections cannot start because the
After snapshotting my master using hot backup to create a workable
slave instance, I created recovery.conf on the slave and tried to get
it to connect to the master and stream WAL.
This led to the message sorry, too many standbys already, which did
not immediately clue me in as to what I needed
On Tue, Mar 30, 2010 at 9:48 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Wed, Mar 31, 2010 at 9:47 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 30, 2010 at 5:09 AM, Fujii Masao masao.fu...@gmail.com wrote:
I rebased the patch to HEAD. Is the patch still required for 9.0?
If
On Tue, Mar 30, 2010 at 12:26 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Wed, Mar 3, 2010 at 9:41 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Wed, Feb 24, 2010 at 2:18 PM, Fujii Masao masao.fu...@gmail.com wrote:
If standby_mode is enabled, and neither primary_conninfo nor
On Wed, Mar 31, 2010 at 12:06 PM, Robert Haas robertmh...@gmail.com wrote:
After snapshotting my master using hot backup to create a workable
slave instance, I created recovery.conf on the slave and tried to get
it to connect to the master and stream WAL.
This led to the message sorry, too
On Wed, Mar 31, 2010 at 12:21 PM, Robert Haas robertmh...@gmail.com wrote:
I just tested this and it seems to just sit there doing this over and
over again:
LOG: record with zero length at 0/3006B28
I'm not sure that we should forbid this configuration, but the current
behavior doesn't
For now Postgres able to create deferrable uniques with following syntax:
...
and table_constraint is:
[ CONSTRAINT constraint_name ]
{ UNIQUE ( column_name [, ... ] ) index_parameters |
PRIMARY KEY ( column_name [, ... ] ) index_parameters |
CHECK ( expression ) |
FOREIGN KEY (
Josh Berkus wrote:
On 3/29/10 5:04 PM, Magnus Hagander wrote:
Last i heard from Dave on that topic is that there's no chance of that
happening that quickly. He's on a plane now but I'm sure he'll confirm
that when he lands.
That means that we'll be doing the test-fest using Alpha4,
49 matches
Mail list logo
