On Fri, Aug 11, 2006 at 05:27:46PM -0400, Alvaro Herrera wrote:
Does that rails thing also have a bug tracker that integrates with
mailing lists? IIRC the show-stopper on a bug tracker was finding one
that allowed people to still use mailing lists.
AFAIU the showstopper was that people
Tom Lane wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
Log Message:
---
Allow commenting of variables in postgresql.conf to restore them to
defaults.
Please revert these patches, as they have broken the build completely
(see buildfarm).
OK, I have backed out both guc
I am still waiting for someone to tell us that they would use this
capability for a real-world problem.
---
Tzahi Fadida wrote:
On Friday 11 August 2006 07:18, Bruce Momjian wrote:
I have looked over this addition, and I
David Fetter wrote:
On Sat, Jul 29, 2006 at 09:14:16PM -0400, Greg Sabino Mullane wrote:
Today on IRC David Fetter and some others were discussing version
numbers and we realized that although libpq now provides the version
of Postgres as a number, this is still a wheel that is being
Tom Lane wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
pgsql/src/pl/plperl/sql:
plperl.sql (r1.7 - r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/sql/plperl.sql.diff?r1=1.7r2=1.8)
Shouldn't there be an 'expected' update to go with the
On Friday 11 August 2006 07:18, Bruce Momjian wrote:
I have looked over this addition, and I think I finally understand it.
Given three tables, A, B, C, which join as A-B, B-C, C-A, you can
really join them as A-B-C, and A-C-B. What full disjunction does is
to perform both of those joins, and
On Saturday 12 August 2006 07:22, Bruce Momjian wrote:
I am still waiting for someone to tell us that they would use this
capability for a real-world problem.
I suggest looking into web applications.
The example here
http://www.technion.ac.il/~tzahi/soc.html
shows a possible 3 separate web
[EMAIL PROTECTED] (Bruce Momjian) writes:
pgsql/src/pl/plperl/sql:
plperl.sql (r1.7 - r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/sql/plperl.sql.diff?r1=1.7r2=1.8)
Shouldn't there be an 'expected' update to go with the test-file update?
The few
[EMAIL PROTECTED] (Bruce Momjian) writes:
Log Message:
---
Allow commenting of variables in postgresql.conf to restore them to
defaults.
Please revert these patches, as they have broken the build completely
(see buildfarm).
regards, tom lane
Currently, psql does not show the command completion tag if it gets a
PGRES_TUPLES_OK result. This means you won't see the tag for a command
with RETURNING, eg
regression=# insert into int8_tbl values(1,2),(3,4);
INSERT 0 2
regression=# insert into int8_tbl values(1,2),(3,4) returning *;
q1 |
Ühel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, K, 2006-08-09 kell 12:56, kirjutas Simon Riggs:
Methinks it should be the Write pointer all of the time, since I can't
think of a valid reason for wanting to know where
Hannu Krosing [EMAIL PROTECTED] writes:
Ãhel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane:
Insert points to the next byte to be written within the internal WAL
buffers. The byte(s) preceding it haven't necessarily gotten out of
those buffers yet. Write points to the end of
A number of the buildfarm machines have been failing HEAD builds
at the make check stage since last night, with complaints like
this one from emu:
== pgsql.21911/src/test/regress/log/postmaster.log
===
FATAL: lock file /tmp/.s.PGSQL.55678.lock already exists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
A friend is getting sig11 on suse linux while trying to establish any
connection to postgresql. Have you seen anything like that? He is using
Postgresql 8.1.4.
He compiled Postgresql with a common ./configure --with--ssl
-
On Fri, Aug 11, 2006 at 10:58:12PM -0400, Tom Lane wrote:
Currently, psql does not show the command completion tag if it gets a
PGRES_TUPLES_OK result. This means you won't see the tag for a command
with RETURNING, eg
regression=# insert into int8_tbl values(1,2),(3,4);
INSERT 0 2
On Fri, Aug 11, 2006 at 05:11:03PM -0500, Jim C. Nasby wrote:
On Fri, Aug 11, 2006 at 10:59:45AM -0400, Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian wrote:
Are we sure we don't want the patch for a non-subquery version of SET
ROW for 8.2?
o Allow UPDATE
On Sat, Aug 12, 2006 at 11:29:46AM -0400, Tom Lane wrote:
What's happened is that that GUC patch that was in the tree for a few
hours broke postmaster startup on some machines (for as-yet-unidentified
reasons). The postmaster does actually start and establish its
lockfiles, but it never gets
It has just been pointed out to me that the list archives seem to have
stopped being updated last Wednesday. Any idea why?
cheers
andrew
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose
Hello -hackers,
I recently have seen the segfault with Postgres 8.1.4.
The situation in which the segfault occur is quite complicated (a lot of
commands in one transaction from JDBC), but Here I show the gdb core dump of
it. From looking in my application, it seems that the core dump occurs
Tom Lane wrote:
A number of the buildfarm machines have been failing HEAD builds
at the make check stage since last night, with complaints like
this one from emu:
== pgsql.21911/src/test/regress/log/postmaster.log
===
FATAL: lock file
On Aug 12, 2006, at 6:01 , Tzahi Fadida wrote:
On Saturday 12 August 2006 07:22, Bruce Momjian wrote:
I am still waiting for someone to tell us that they would use this
capability for a real-world problem.
Notice that if you google full disjunction that the first link is
this project.
Francisco Figueiredo Jr. wrote:
Hi all,
A friend is getting sig11 on suse linux while trying to establish any
connection to postgresql. Have you seen anything like that? He is using
Postgresql 8.1.4.
He compiled Postgresql with a common ./configure --with--ssl
- --prefix=/usr/local
After
AgentM wrote:
On Aug 12, 2006, at 6:01 , Tzahi Fadida wrote:
On Saturday 12 August 2006 07:22, Bruce Momjian wrote:
I am still waiting for someone to tell us that they would use this
capability for a real-world problem.
Notice that if you google full disjunction that the first link
Fixed ... the 'auto run' was commented out when I was rebuilding it all
for the pre-July / post-July changes (old vs new) and failed to uncomment
the cron job after ...
should be updated within the next hour or so ...
On Sat, 12 Aug 2006, Andrew Dunstan wrote:
It has just been pointed
AgentM [EMAIL PROTECTED] writes:
You won't find anyone to vouch for it because this is the first
implementation of full disjunctions in any database. That doesn't
mean it isn't useful- it means no one is using it because it hasn't
existed until now.
This is the point where one needs to
Sergey E. Koposov [EMAIL PROTECTED] writes:
I recently have seen the segfault with Postgres 8.1.4.
I'm betting that portal-sourceText has already been deallocated when
exec_execute_message tries to print the log message. Getting an actual
segfault from that would very probably be hard to
On 8/12/06, Tom Lane [EMAIL PROTECTED] wrote:
More seriously: the current state of affairs is that the
full-disjunction code exists as a pgfoundry project. If it's indeed the
second greatest thing since sliced bread, then I think we could assume
that people will find it and use it from
On Friday 04 August 2006 02:20, Josh Berkus wrote:
grin Aren't I, the marketing geek, supposed to be the one whining about
this?
[snip]
* In-place upgrades (pg_upgrade)
BTW, I may get Sun to contribute an engineer for this; will get you posted.
Long time no post. This statement really
On Sat, 12 Aug 2006, Tom Lane wrote:
Sergey E. Koposov [EMAIL PROTECTED] writes:
I recently have seen the segfault with Postgres 8.1.4.
I'm betting that portal-sourceText has already been deallocated when
exec_execute_message tries to print the log message. Getting an actual
segfault from
Ühel kenal päeval, L, 2006-08-12 kell 10:59, kirjutas Tom Lane:
Hannu Krosing [EMAIL PROTECTED] writes:
Ühel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane:
Insert points to the next byte to be written within the internal WAL
buffers. The byte(s) preceding it haven't necessarily
30 matches
Mail list logo
