On Mon, Aug 28, 2006 at 07:35:11PM +0200, Zoltan Boszormenyi wrote:
> >>COPY (SELECT ...) (col1, col2, ...) TO
> >>and it was actually working. In your v9
> >>you rewrote the syntax parsing so that
> >>feature was lost in translation.
> >>
> >
> >Interesting. I didn't realize this was possible
Guillaume Smet wrote:
> On 8/29/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > Good point. I thought it was clear enough, but obviously not. I had a
> > similar case with bind, and used a comma to separate them:
> >
> > LOG: statement: prepare sel1, SELECT $1;
> > LOG: stateme
=?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= <[EMAIL PROTECTED]> writes:
> as per your suggestion, the COPY view TO support was cut and
> a hint was added. Please, review.
Committed after some refactoring to avoid code duplication.
Unfortunately, in a moment of pure brain fade, I looked at the wro
Tom Lane wrote:
> =?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= <[EMAIL PROTECTED]> writes:
> > as per your suggestion, the COPY view TO support was cut and
> > a hint was added. Please, review.
>
> Committed after some refactoring to avoid code duplication.
>
> Unfortunately, in a moment of pure b
Thanks!!!
Tom Lane írta:
=?iso-8859-2?Q?B=F6sz=F6rm=E9nyi_Zolt=E1n?= <[EMAIL PROTECTED]> writes:
as per your suggestion, the COPY view TO support was cut and
a hint was added. Please, review.
Committed after some refactoring to avoid code duplication.
Unfortunately, in a moment of pu
On 8/29/06, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Good point. I thought it was clear enough, but obviously not. I had a
similar case with bind, and used a comma to separate them:
LOG: statement: prepare sel1, SELECT $1;
LOG: statement: bind sel1, $1 = 'a''b'
For this one
On Tue, Aug 29, 2006 at 02:46:06PM -0400, Chris Browne wrote:
> I'm not at all sure that these are the right changes to apply; it
> somewhat appears to me as though ecpg is supposed to be able to cope
> with the omissions.
Yor're right. It should cope with those. The database names were
ommitted b
On Tue, 2006-08-29 at 18:31 -0400, Tom Lane wrote:
> <[EMAIL PROTECTED]> writes:
> > here comes the latest version (version 7) of the patch to handle large
> > result sets with psql. As previously discussed, a cursor is used
> > for SELECT queries when \set FETCH_COUNT some_value > 0
>
> Applied
accelerator support) to use.
diff -crN ../pgsql-20060830/doc/src/sgml/config.sgml ./doc/src/sgml/config.sgml
*** ../pgsql-20060830/doc/src/sgml/config.sgml 2006-08-30 16:01:12.0
+0400
--- ./doc/src/sgml/config.sgml 2006-08-30 16:04:11.0 +0400
***
*** 555,561
On Aug 30, 2006, at 12:50 , Bruce Momjian wrote:
Yea, I see that -122:23:60.00.
After applying your patch, I believe that on my machine it's the
contribution from the day component that is producing the 23:60.00.
For example,
select interval '-12 days' * 0.3;
?column?
---
"Victor B. Wagner" <[EMAIL PROTECTED]> writes:
> This patch adds two new configuration diretives to postgresql.conf file
> 1. ssl_ciphers - allows server administrator to specify set of SSL
> ciphersuites which can be used by clients to connect the server.
> 2. ssl_engine - allows to specify lo
On 2006.08.30 at 10:14:02 -0400, Tom Lane wrote:
> "Victor B. Wagner" <[EMAIL PROTECTED]> writes:
> > This patch adds two new configuration diretives to postgresql.conf file
> > 1. ssl_ciphers - allows server administrator to specify set of SSL
> > ciphersuites which can be used by clients to co
On Wed, Aug 30, 2006 at 12:01:25PM -0400, Tom Lane wrote:
> Bernd Helmle <[EMAIL PROTECTED]> writes:
> > [ latest views patch ]
>
> This is the first time I've actually looked at this patch, and I am
> dismayed. viewUpdate.c looks like nothing so much as a large program
> with a small program str
Bernd Helmle <[EMAIL PROTECTED]> writes:
> [ latest views patch ]
This is the first time I've actually looked at this patch, and I am
dismayed. viewUpdate.c looks like nothing so much as a large program
with a small program struggling to get out. What is all the stuff about
handling multiple bas
Michael Glaesemann wrote:
> > Yea, just an optimization, but I was worried that the computations
> > might
> > throw problems for certain numbers, so I figured I would only
> > trigger it
> > when necessary.
>
> Thanks for the explanation. Helps me know I might actually be
> learning this.
>
Michael Glaesemann wrote:
>
> On Aug 30, 2006, at 12:50 , Bruce Momjian wrote:
>
> > Yea, I see that -122:23:60.00.
>
> After applying your patch, I believe that on my machine it's the
> contribution from the day component that is producing the 23:60.00.
> For example,
>
> select interval '
16 matches
Mail list logo
