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 because
On Fri, 22 Aug 2008 08:23:01 +0200
Martijn van Oosterhout [EMAIL PROTECTED] wrote:
On Thu, Aug 21, 2008 at 11:18:24PM -0400, D'Arcy J.M. Cain wrote:
ReST is nice because it's almost plain text. In fact, a ReST document
source can easily be read raw.
I presume by ReST you mean this:
A Divendres 22 Agost 2008, Alvaro Herrera va escriure:
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
Tom Lane wrote:
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
Ah.. my definition of MDT was flawed; thanks for the help!
Alvaro Herrera wrote:
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
On Fri, Aug 22, 2008 at 10:10 AM, Alvaro Herrera
[EMAIL PROTECTED] 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
On Aug 20, 2008, at 9:18 AM, Tom Lane wrote:
However I have no hard evidence to back up drawing the line there
rather
than somewhere else. Anyone have data on what sort of DDL changes are
common in their applications?
I've worked in environments where we used stored functions
extensively
On Aug 20, 2008, at 12:43 PM, Tom Lane wrote:
We have speculated in the past about having alternative plans that
could be conditionally executed based on information not available
at planning time. This could be seen as a first experiment in that
direction. I am not thinking of a
Are we still tracking beginner TODOs separately? I'm thinking this
falls into that category...
Barring objection, I'll mark it as easy.
On Aug 21, 2008, at 5:38 PM, Bruce Momjian wrote:
Added to TODO:
Allow GRANT/REVOKE on views to use the VIEW keyword rather
than just
On Aug 20, 2008, at 8:26 AM, Pavel Stehule wrote:
2008/8/20 Tom Lane [EMAIL PROTECTED]:
Pavel Stehule [EMAIL PROTECTED] writes:
I understand now why Oracle use = symbol for named params. This
isn't
used so operator - so implementation is trivial.
You really didn't understand the objection
On Aug 12, 2008, at 2:43 PM, Greg Smith wrote:
On Tue, 12 Aug 2008, Bruce Momjian wrote:
There's already some changes needed in this area needed to
execute the
full GUC cleanup/wizard plan that's being worked on. The
pg_settings view
really should show the value both as the user input it
Decibel! wrote:
Are we still tracking beginner TODOs separately? I'm thinking this
falls into that category...
Barring objection, I'll mark it as easy.
I already had; markers just don't cust/paste easily like they used to.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
depends if you think hacking the bison grammar is a beginner task.
cheers
andrew
Decibel! wrote:
Are we still tracking beginner TODOs separately? I'm thinking this
falls into that category...
Barring objection, I'll mark it as easy.
On Aug 21, 2008, at 5:38 PM, Bruce Momjian wrote:
Garick Hamlin wrote:
On Thu, Jul 03, 2008 at 02:01:22PM -0400, Tom Lane wrote:
Garick Hamlin [EMAIL PROTECTED] writes:
I have a patch that I have been using to support postgresql's
notion of ident authentication when using unix domain sockets on
Solaris. This patch basically
Hi,
While we're on this topic, I think we need put a link at [1] heading
directly to (Official) Todo [2]. What we have ATM is Unofficial Todo
Detail that is rather inconsistent. We should rename it to Todo
Detail. Comments?
[1] http://wiki.postgresql.org/wiki/Development_information
[2]
On Fri, 22 Aug 2008 14:28:57 -0300
Euler Taveira de Oliveira [EMAIL PROTECTED] wrote:
Hi,
While we're on this topic, I think we need put a link at [1] heading
directly to (Official) Todo [2]. What we have ATM is Unofficial Todo
Detail that is rather inconsistent. We should rename it to Todo
Euler Taveira de Oliveira wrote:
Hi,
While we're on this topic, I think we need put a link at [1] heading
directly to (Official) Todo [2]. What we have ATM is Unofficial Todo
Detail that is rather inconsistent. We should rename it to Todo
Detail. Comments?
[1]
People,
I am converting C++ code to Postgres.
Need help on how to deal with mysql_fetch_row, mysql_store_result
functions in Postgres? There should be some C/C++ code available for
these things, I hope.
Thanks,
Alex.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
On Fri, Aug 22, 2008 at 2:20 PM, Masis, Alexander (US SSA)
[EMAIL PROTECTED] wrote:
People,
I am converting C++ code to Postgres.
Need help on how to deal with mysql_fetch_row, mysql_store_result
functions in Postgres? There should be some C/C++ code available for
these things, I hope.
Peter, have you completed this yet?
---
Peter Eisentraut wrote:
Am Mittwoch, 9. Juli 2008 schrieb Peter Eisentraut:
I propose that we relax these two checks to test for binary-coercibility
instead, which is effectively
On Fri, 2008-08-22 at 12:42 -0400, Andrew Dunstan wrote:
depends if you think hacking the bison grammar is a beginner task.
It may be anything from beginners task to quite complex . Some things
are just copypaste.
-
Hannu
--
Sent via pgsql-hackers mailing list
On Thu, 2008-08-21 at 23:41 -0500, Decibel! wrote:
On Aug 20, 2008, at 8:26 AM, Pavel Stehule wrote:
How about we poll -general and see what people say? I'll bet Tom a
beer that no one replies saying they've created a = operator (unless
maybe PostGIS uses it).
Does Oracle use = for
How about we poll -general and see what people say? I'll bet Tom a
beer that no one replies saying they've created a = operator (unless
maybe PostGIS uses it).
Hstore uses it:
* text = text - creates hstore type from two text strings
select 'a'='b';
?column?
--
a=b
--
Teodor
On Sat, 23 Aug 2008 00:03:16 +0400
Teodor Sigaev [EMAIL PROTECTED] wrote:
select 'a'='b';
?column?
--
a=b
Branching the topic, I have a question about this. I haven't studied
hstore extensively but this seems like a problem on it's face.
Shouldn't you be able to take the result
I think I may have found another bug:
WITH RECURSIVE t(i,j) AS (
VALUES (1,2)
UNION ALL
SELECT t2.i, t.j
FROM (
SELECT 2 AS i
UNION ALL /* Wrongly getting detected, I think */
SELECT 3 AS i
) AS t2
JOIN
t
ON (t2.i
Added to September commit fest.
---
Abhijit Menon-Sen wrote:
At 2008-07-09 15:11:25 -0400, [EMAIL PROTECTED] wrote:
No, actually I meant having a lone list = lappend(list, newseq); in
the loop, so that
I assume there is no TODO here.
---
Pavan Deolasee wrote:
(taking the discussions to -hackers)
On Sat, Jul 12, 2008 at 11:02 PM, Tom Lane [EMAIL PROTECTED] wrote:
(2) It achieves speedup of VACUUM by pushing work
27 matches
Mail list logo