Andrew Hammond wrote:
> I need to write a perl module which will parse a .pgpass file into a
> reasonable data-structure in memory. I may extend it later to go in the
> other direction (given a populated datastructure, write a .pgpass).
>
> The first question that came to mind is what namespace sho
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
> reinvented by apps many ti
On Aug 10, 2006, at 7:57 AM, Tom Lane wrote:
Anyway, after further thought I've concluded that we really should
supply something that returns the Insert pointer, as this would be
useful for debugging and system-monitoring purposes. It's clear
however
that we also need something that returns t
11 Aug 2006 15:57:42 -0700, Andrew Hammond <[EMAIL PROTECTED]>:
I need to write a perl module which will parse a .pgpass file into a
reasonable data-structure in memory. I may extend it later to go in the
other direction (given a populated datastructure, write a .pgpass).
The first question that
I need to write a perl module which will parse a .pgpass file into a
reasonable data-structure in memory. I may extend it later to go in the
other direction (given a populated datastructure, write a .pgpass).
The first question that came to mind is what namespace should I put
this under? Is there
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 tab SET ROW (col, ...) = (...) for updating
> > > multi
Jim C. Nasby wrote:
> On Fri, Aug 11, 2006 at 08:16:19AM -0700, Joshua D. Drake wrote:
> > I just threw the trac out there because it was already setup. I don't
> > care if anyone uses it or not. Nor am I suggesting that it *should* be used.
> >
> > Lastly if you review this thread you would see
On Fri, Aug 11, 2006 at 08:16:19AM -0700, Joshua D. Drake wrote:
> I just threw the trac out there because it was already setup. I don't
> care if anyone uses it or not. Nor am I suggesting that it *should* be used.
>
> Lastly if you review this thread you would see that Andrew and I had
> alrea
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 8/11/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> 4. Treat PORTAL_ONE_RETURNING like PORTAL_UTIL_SELECT rather than
>> like PORTAL_ONE_SELECT; that is, execute the query to completion
>> on first call and stash the results in a tuplestore until the
>
Gregory Stark wrote:
>
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>
> > I use more or less what is in the developers' FAQ (not surprising, since I
> > contributed it). It works just fine for me. See
> > http://www.postgresql.org/docs/faqs.FAQ_DEV.html#item1.9
> >
> > We should probably bring t
Patch applied. Thanks. Unnecessary #include file removed.
---
David Fetter wrote:
> On Sun, Jul 30, 2006 at 05:40:16PM -0400, Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > David Fetter wrote:
> > >
I have found the cause.
The source file func.pgc is in DOS format, using CRLF(\r\n, or 0x0D0A) as
the newline character(s). That's why I got the output:
$ make func.o
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-
statement -Wendif-labels -fno-strict-aliasing -g
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> I use more or less what is in the developers' FAQ (not surprising, since I
> contributed it). It works just fine for me. See
> http://www.postgresql.org/docs/faqs.FAQ_DEV.html#item1.9
>
> We should probably bring the docs in line with that, unless som
[EMAIL PROTECTED] (Paul Silveira) writes:
> Does anyone have any good examples of implementing "snapshot"
> replication. I know that PostgreSQL does not have snapshot
> replication and that Slony-I is the recomended replication senario
> but I've configured it and it seems rather advanced for a sho
On 8/11/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Not really. Locks and so forth held by the query would be held till
commit in any case, so I don't see much advantage in finishing the
query immediately.
Very true.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corpor
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 8/11/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> 4. Treat PORTAL_ONE_RETURNING like PORTAL_UTIL_SELECT rather than
>> like PORTAL_ONE_SELECT; that is, execute the query to completion
>> on first call and stash the results in a tuplestore until the
>
> 1. Define it as a feature not a bug. People do occasionally ask for
> "UPDATE foo ... LIMIT 1" after all. But this is a pretty klugy way of
> getting that, and the arguments that say allowing LIMIT on updating
> queries would be a bad idea haven't lost their force.
Being one of those who was a
Sorry, copied to list.
On 8/11/06, Tom Lane <[EMAIL PROTECTED]> wrote:
3. Throw an error (thereby rolling back the incomplete update)
if client closes the portal without having run it to completion.
Sounds like the most reasonable considering. I'm not averse to it.
4. Treat PORTAL_ONE_RETUR
I'm looking at modifying the portal execution strategy so that INSERT
RETURNING and friends will work when invoked through "extended query"
protocol. Currently, INSERT/UPDATE/DELETE queries are always executed
under PORTAL_MULTI_QUERY strategy, which runs the portal's queries to
completion and dis
Actually I'd *like* to use something better than CVSWeb, because you
know what? It sucks and I'd love to have something better. I'd also
I am not opposed to actually using taylor or something to do the
conversion instead. I just couldn't get it to work.
I think the devel version of Trac
Alvaro Herrera wrote:
> > O.k. but no one is suggesting that we use Trac as a bug tracker, or at
> > least I wasn't. All I was suggesting was the ability to help viewing of
> > specific files as listed dependencies.
>
> I am suggesting that. I have heard all the old discussions about not
> usin
Joshua D. Drake wrote:
>
> >>http://projects.commandprompt.com/public/pgsql/browser/tags/REL8_1_4/pgsql
> >>
> >>What are you looking at Alvaro?
> >
> >Exactly that URL, but this wasn't there when I looked. Maybe it was
> >being regenerated at that time?
>
> Yeah it gets regenerated every 4 hour
Due to the bug in bison 2.1, I always use version 1.875:
http://www.mail-archive.com/bug-bison@gnu.org/msg00718.html
""Christopher Kings-Lynne"" <[EMAIL PROTECTED]>
> What version of Bison is currently required to compile HEAD? 1.75
> doesn't seem to work...
>
> ---(en
Joshua D. Drake wrote:
Lastly if you review this thread you would see that Andrew and I had
already decided to wait until after Linux World to actually propose
something.
It is perhaps not surprising, but most of the discussion has been
focused on technologies (mailing lists, wikis, bugt
I do not agree. How you determine what release fixes the bug now? We
have web page and mailing list for bug reporting but there is not any
relation between bug, patch and release(s). I think bug tracking is
necessary if we want move forward.
You can completely forget the idea of having an ac
http://projects.commandprompt.com/public/pgsql/browser/tags/REL8_1_4/pgsql
What are you looking at Alvaro?
Exactly that URL, but this wasn't there when I looked. Maybe it was
being regenerated at that time?
Yeah it gets regenerated every 4 hours or so.
But I don't know why you are ignor
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> On Fri, Aug 11, 2006 at 12:48:27AM -0400, Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Do we want to enable a ICU build option in 8.2?
> >
> > Uh, that wasn't seriously on the table was it? AFAIR we don't have
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 tab SET ROW (col, ...) = (...) for updating
> > multiple columns
>
> It seems to be moderately useful as a notational convenience
Joshua D. Drake wrote:
> Alvaro Herrera wrote:
> >Jim Nasby wrote:
> >>First, +1 on Josh B.'s point about trying out Trac, since it's
> >>already up and running. Josh D., can you just turn that on? (BTW, is
> >>trac linked off http://commandprompt.com anywhere? I had to google to
> >>find it
Neil Conway napsal(a):
However, is there a reason to use Trac beyond the fact that it is
already setup? ISTM we only need a wiki, and don't need the other
features of Trac, such as the bug tracker.
I do not agree. How you determine what release fixes the bug now? We
have web page and mailing
Christopher Kings-Lynne wrote:
What version of Bison is currently required to compile HEAD? 1.75
doesn't seem to work...
Bison >= 1.875 has been required for years. That hasn't changed.
cheers
andrew
---(end of broadcast)---
TIP 3: Have you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> What version of Bison is currently required to compile HEAD? 1.75
> doesn't seem to work...
1.875
Search for Bison here:
http://projects.commandprompt.com/public/pgsql/browser/trunk/pgsql/doc/src/sgml/installation.sgml
- --
Greg Sabino Mullane
On Aug 11 12:51, Greg Sabino Mullane wrote:
> > think it would be quite handy to be able to gather information about
> > a prepared stmt in later phases of an application. For instance one
> > might need to get the parameter and row types of a prepared query
> > that he/she isn't created.
>
> Prep
What version of Bison is currently required to compile HEAD? 1.75
doesn't seem to work...
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> think it would be quite handy to be able to gather information
> about a prepared stmt in later phases of an application. For
> instance one might need to get the parameter and row types of
> a prepared query that he/she isn't created.
Prepared st
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> What's [the difference between] a record (which is a pseudo 'p' type) and
> a rowtype (which's a complex 'c' type).
The main difference is that you can't declare a table column as having
a pseudotype. RECORD is restricted to uses where the system can
de
Hello,
Does anyone have any good examples of implementing "snapshot" replication.
I know that PostgreSQL does not have snapshot replication and that Slony-I
is the recomended replication senario but I've configured it and it seems
rather advanced for a shop that is implementing PostgreSQL for th
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 tab SET ROW (col, ...) = (...) for updating
> multiple columns
It seems to be moderately useful as a notational convenience for now.
Is it too hard to rip it back
Hi,
What's [the difference between] a record (which is a pseudo 'p' type) and
a rowtype (which's a complex 'c' type).
Regards.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Reinoud van Leeuwen wrote:
On Thu, Aug 10, 2006 at 09:02:36PM -0700, Joshua D. Drake wrote:
I think it is a combination of the two. A wiki could be used to discuss
ideas for todos, it could be used to describe TODOs in actual detail, it
could used (in conjunction with Trac) to be able to docu
On Thu, Aug 10, 2006 at 09:02:36PM -0700, Joshua D. Drake wrote:
> I think it is a combination of the two. A wiki could be used to discuss
> ideas for todos, it could be used to describe TODOs in actual detail, it
> could used (in conjunction with Trac) to be able to document dependecies
> for
On Aug 10 11:35, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > [ patch to add PQdescribePrepared and PQdescribePortal ]
>
> After looking this over, I don't see the point of PQdescribePortal,
> at least not without adding other functionality to libpq. There is
> no functionality
On Thu, 2006-08-10 at 08:57 -0400, Tom Lane wrote:
> Anyway, after further thought I've concluded that we really should
> supply something that returns the Insert pointer, as this would be
> useful for debugging and system-monitoring purposes. It's clear however
> that we also need something that
43 matches
Mail list logo
