On Thu, Aug 21, 2008 at 11:18:24PM -0400, D'Arcy J.M. Cain wrote:
> > I think it does -- I used to use the Latex output format for easy cut'n
> > pasting. ReST sounds like it serves the same purpose. If I had had to
> > use conversion to XML, it would have been rather painful.
>
> ReST is nice b
Hi, thanks for your reply.
Tom Lane wrote:
>> If a user who perform "pg_ctl -w start" does not have authority to connect
>> postgres-database, pg_ctl will return 1 and show "could not start server"
>> message.
>
> You didn't say what auth method you are using
The problem that I showed occurs in f
2008/8/21 Asko Oja <[EMAIL PROTECTED]>:
> Would AS be harder to implement?
>
> select foo(10 AS a, 20 AS b);
> select foo(20 AS b, 20 AS a);
> select x(0 >= 1 AS a);
>
> other fantasies
> select foo(10 a, 20 b);
> select foo("a" 10, "b" 20);
no, I have it. Problem is in semantic. There are two fea
On Thu, 21 Aug 2008 21:19:58 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Tom Lane escribió:
> > There's still the question of whether this covers any needs that aren't
> > met just as well by XML or CSV output formats.
>
> I think it does -- I used to use the Latex output format for easy cut
Bruce Momjian <[EMAIL PROTECTED]> writes:
> ALTER DATABASE ... SET seems to be something that doesn't fit in
> anywhere; I am thinking pg_dump -g should dump it.
The upthread conclusion was that pg_dump -C should do it.
I am not sure how you come to the conclusion that -g is an
appropriate place,
Robert Treat wrote:
> On Thursday 21 August 2008 18:28:55 Bruce Momjian wrote:
> > We never came up with any idea of how pg_dump could dump ALTER DATABASE
> > ... SET commands, so I have added a mention in the documentation, and
> > backpatched to 8.3.X; attached.
> >
>
> ok, I have no recollecti
bruce wrote:
> Tom Lane wrote:
> > Currently, config.sgml still describes the new "enum" GUC variables
> > as being of type "string" --- but pg_settings says they are "enum".
> > This is not very consistent, but I wonder whether changing the docs
> > would be more confusing or less so. I note that
On Thursday 21 August 2008 18:28:55 Bruce Momjian wrote:
> We never came up with any idea of how pg_dump could dump ALTER DATABASE
> ... SET commands, so I have added a mention in the documentation, and
> backpatched to 8.3.X; attached.
>
ok, I have no recollection of this conversation :-)
but..
Tom Lane wrote:
> Currently, config.sgml still describes the new "enum" GUC variables
> as being of type "string" --- but pg_settings says they are "enum".
> This is not very consistent, but I wonder whether changing the docs
> would be more confusing or less so. I note that section 18.1 doesn't
>
Tom Lane escribió:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > On Thu, 21 Aug 2008 23:22:28 +0300
> > "Asko Oja" <[EMAIL PROTECTED]> wrote:
> >> The idea would be to use psql as backend for some other system?
> >> Or what do you mean by fed directly?
>
> > No, I meant that one would do an
Tom Lane wrote:
> Dave Witt <[EMAIL PROTECTED]> writes:
> > These two queries produce different output, using version 8.3.3:
> > SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'MDT';
> > SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'America/Boise';
>
> Why are you surprised
Alvaro Herrera wrote:
> Alvaro Herrera escribi?:
>
> > They did not merge with the text, but they were not searchable. May I
> > suggest using the text "[easy]" and "[done]" instead? That way, it is
> > searchable, and they don't merge with the text.
>
> I just made this change. What I now not
On Thu, 21 Aug 2008 20:36:51 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > No, I meant that one would do any ad hoc query and cut and paste the
> > output directly into a tracking tool that supports ReST.
>
> There's still the question of whether th
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Alvaro Herrera escribió:
>> They did not merge with the text, but they were not searchable. May I
>> suggest using the text "[easy]" and "[done]" instead? That way, it is
>> searchable, and they don't merge with the text.
> I just made this change. W
Dave Witt <[EMAIL PROTECTED]> writes:
> These two queries produce different output, using version 8.3.3:
> SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'MDT';
> SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'America/Boise';
Why are you surprised? Boise would've been on MS
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO:
> Eliminate de-TOASTing of values when not needed
That's a fairly bad description of what the patch was about. I changed
it to
Reduce costs of repeat de-TOASTing of values
regards, tom lane
--
Sen
Bruce Momjian <[EMAIL PROTECTED]> writes:
> The TODO link on the developer page needs to be updated too:
> http://www.postgresql.org/developer/
Also, is this page still sane?
http://wiki.postgresql.org/wiki/Todo:Contents
If it is, I suggest it be renamed to TodoDetail or some such.
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> On Thu, 21 Aug 2008 23:22:28 +0300
> "Asko Oja" <[EMAIL PROTECTED]> wrote:
>> The idea would be to use psql as backend for some other system?
>> Or what do you mean by fed directly?
> No, I meant that one would do any ad hoc query and cut and paste
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> Introduce JOIN_SEMI and JOIN_ANTI join types, the former replacing
>> JOIN_IN.
> It just struck me that this may cause additional joins to count
> against the join_collapse_limit. If so, that could cause some
Alvaro Herrera escribió:
> They did not merge with the text, but they were not searchable. May I
> suggest using the text "[easy]" and "[done]" instead? That way, it is
> searchable, and they don't merge with the text.
I just made this change. What I now notice is that both markers are
visuall
Wording adjusted and applied with attached patch.
---
Gurjeet Singh wrote:
> On Mon, Jun 30, 2008 at 7:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > In any case, this seem
Bruce Momjian escribió:
> Albert Cervera i Areny wrote:
> > That doesn't make it easily searchable. Maybe I'm the only one, but every
> > now
> > and then I take a look at it, and there's no fast way of seeing what items
> > have been done (and marked as easier).
>
> That is true, but text li
Albert Cervera i Areny wrote:
> A Divendres 22 Agost 2008, Bruce Momjian va escriure:
> > Albert Cervera i Areny wrote:
> > > A Dimecres 20 Agost 2008, Alvaro Herrera va escriure:
> > > > Hi,
> > > >
> > > > Thanks to Brendan Jurd, who spent a lot of effort in creating useful
> > > > Mediawiki temp
A Divendres 22 Agost 2008, Bruce Momjian va escriure:
> Albert Cervera i Areny wrote:
> > A Dimecres 20 Agost 2008, Alvaro Herrera va escriure:
> > > Hi,
> > >
> > > Thanks to Brendan Jurd, who spent a lot of effort in creating useful
> > > Mediawiki templates, we now have moved the TODO list to th
Albert Cervera i Areny wrote:
> A Dimecres 20 Agost 2008, Alvaro Herrera va escriure:
> > Hi,
> >
> > Thanks to Brendan Jurd, who spent a lot of effort in creating useful
> > Mediawiki templates, we now have moved the TODO list to the Wiki site.
> >
> > The new official location for the TODO list i
Added to TODO:
Allow GRANT/REVOKE on views to use the VIEW keyword rather
than just TABLE
http://archives.postgresql.org/pgsql-hackers/2008-06/msg01133.php
---
Bruce Momjian wrote:
> Marc Munro wr
We never came up with any idea of how pg_dump could dump ALTER DATABASE
... SET commands, so I have added a mention in the documentation, and
backpatched to 8.3.X; attached.
---
Richard Huxton wrote:
> Robert Treat wrote:
>
A Dimecres 20 Agost 2008, Alvaro Herrera va escriure:
> Hi,
>
> Thanks to Brendan Jurd, who spent a lot of effort in creating useful
> Mediawiki templates, we now have moved the TODO list to the Wiki site.
>
> The new official location for the TODO list is here:
> http://wiki.postgresql.org/wiki/To
These two queries produce different output, using version 8.3.3:
SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'MDT';
SELECT '2008-01-01 00:00:00+00'::timestamptz AT TIME ZONE 'America/Boise';
..is this a bug?
Note: "America/Boise"="MDT" (from pg_timezone_names)
Best regards,
--
Bruce Momjian wrote:
> The TODO link on the developer page needs to be updated too:
>
> http://www.postgresql.org/developer/
Done too (and a few other links to the TODO list that are on the
website).
Minor nit: the summer of code page says that the easy items are marked
with a %, but that
Added to TODO:
Eliminate de-TOASTing of values when not needed
---
Tom Lane wrote:
> Attached is a worked-out patch for the approach proposed here:
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00777.php
On Thu, 21 Aug 2008 23:22:28 +0300
"Asko Oja" <[EMAIL PROTECTED]> wrote:
> The idea would be to use psql as backend for some other system?
> Or what do you mean by fed directly?
No, I meant that one would do any ad hoc query and cut and paste the
output directly into a tracking tool that supports
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > Peter Eisentraut wrote:
> > >> Plus, a URL such as http://wiki.postgresql.org/wiki/Todo would be a
> > >> lot more obvious to find.
> >
> > > Moved. The old name is kept as a redirect.
> >
> > Pls make
Proposed formats don't look easier to read for humans.
I doubt that they are more common or easier to process by machines than just
COPY query TO STDOUT CSV;
> The reason for this is to allow the output to be fed directly into any
> system using Restructured text
The idea would be to use psql as
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> Plus, a URL such as http://wiki.postgresql.org/wiki/Todo would be a
> >> lot more obvious to find.
>
> > Moved. The old name is kept as a redirect.
>
> Pls make doc/TODO match.
Done.
--
Alvaro Herre
Would AS be harder to implement?
select foo(10 AS a, 20 AS b);
select foo(20 AS b, 20 AS a);
select x(0 >= 1 AS a);
other fantasies
select foo(10 a, 20 b);
select foo("a" 10, "b" 20);
regards,
Asko
On Wed, Aug 20, 2008 at 4:26 PM, Pavel Stehule <[EMAIL PROTECTED]>wrote:
> 2008/8/20 Tom Lane <[
On Thu, 21 Aug 2008 15:03:23 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > I would like to propose a new border setting.
>
> That code is horrendously overcomplicated and unreadable already :-(
> I'm not too eager to add more variants to it.
Actual
>>> Tom Lane <[EMAIL PROTECTED]> wrote:
> Introduce JOIN_SEMI and JOIN_ANTI join types, the former replacing
> JOIN_IN. Unify the InClauseInfo and OuterJoinInfo infrastructure
into
> "SpecialJoinInfo". Convert IN, EXISTS, and NOT EXISTS clauses at
top
> level of WHERE into semi and anti joins
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Plus, a URL such as http://wiki.postgresql.org/wiki/Todo would be a
>> lot more obvious to find.
> Moved. The old name is kept as a redirect.
Pls make doc/TODO match.
regards, tom lane
--
Sent via
"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> I would like to propose a new border setting.
That code is horrendously overcomplicated and unreadable already :-(
I'm not too eager to add more variants to it.
> The reason for this is to allow the output to be fed directly into any
> system using
Hi,
Marcelo Martins wrote:
Anyone knows a link that has some docs about how to get that setup ?
Besides the README and other documentation in the source, there's
admittedly not much. Check the archive of this mailing list.
Also is it stable enough for production ?
No.
I though getting p
Peter Eisentraut wrote:
> Plus, a URL such as http://wiki.postgresql.org/wiki/Todo would be a
> lot more obvious to find.
Moved. The old name is kept as a redirect.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Peter Eisentraut wrote:
> Alvaro Herrera wrote:
> > The new official location for the TODO list is here:
> > http://wiki.postgresql.org/wiki/Todo:Todo
>
> What is it with this strange page naming?
I agree with your argument. I think we inherited this name from a very
old attempt to do the conver
Alvaro Herrera wrote:
> The new official location for the TODO list is here:
> http://wiki.postgresql.org/wiki/Todo:Todo
What is it with this strange page naming? Have we not established some time
ago that the colon is only supposed to be used for metapages? We kind of
blew this on the commit
Here is a simple select output.
darcy=# select title_id, title_name from title;
title_id | title_name
--+
2 | Mrs
3 | Ms
4 | Miss
(3 rows)
Now I change the border.
darcy=# \pset border 2
Border style is 2.
darcy=# select title_id, title_name from tit
Alvaro Herrera wrote:
> So, did anyone else try to generate man pages?
Before we get too excited here: Man pages are only built/buildable from
elements. You can't just go and convert some arbitrary section or
chapter into a man page. So there is a bit of work and invention necessary
here.
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> If I understand correctly then for read path (select) tuple is always
> HeapTuple, because we need support select xmax ... And DatumTuple is
> used for write path (insert/update) and it is "converted" to HeapTuple
> in heap_insert/heap_update function.
Tatsuhito Kasahara <[EMAIL PROTECTED]> writes:
> If a user who perform "pg_ctl -w start" does not have authority to connect
> postgres-database, pg_ctl will return 1 and show "could not start server"
> message.
pg_ctl is already set up to recognize bad-password errors as meaning the
postmaster is
Hi.
When we perform "pg_ctl -w start", postgres try to connect to
postgres-database until timeout.
If a user who perform "pg_ctl -w start" does not have authority to connect
postgres-database, pg_ctl will return 1 and show "could not start server"
message.
But, in fact server is already starting
David Fetter wrote:
> And we're back to man pages and CHM files.
So, did anyone else try to generate man pages? I did "make man" and ran
into several issues.
The first is that D2MDIR needs to be specified manually. I assume this
is how everyone does it, so I did that.
The second is that the P
Tom Lane wrote:
Of course, since you got the data migrated you might not care anymore.
That's what i've done:
1. pg_dump database from 6.5.3
2. iconv from windows-1251 charset to utf-8.
3. cutted all AGGREGATEs
4. succesefully imported all data to 8.3.1 without errors.
Seems to me everything n
David Fetter wrote:
> And we're back to man pages and CHM files.
>
> How big a project would that latter be?
CHM files already exist. (At least I think that CHM == HTML Help == Windows
help system.)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your s
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I try to understand why HeapTupleHeaderData structure has t_datum
member. This is use only on few places and from my point of view this
information should be stored in the HeapTupleData structure or split
HeapTupleHeaderData it into
On Wed, Aug 20, 2008 at 9:15 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
> > Idly thumbing through the new TODO list, I noticed that the second item
> > from the bottom (about how we don't want optional AS) has been
> > superseded by events ...
> > http://archives.postgresql.org
54 matches
Mail list logo
