On 2006.08.31 at 00:09:56 +0200, Peter Eisentraut wrote:
> Victor B. Wagner wrote:
> > First one is useful if for some reason some ciphers supported by
> > OpenSSL is not permitted to use in the particular network, or if
> > there is need to use ciphersuites which are not included into default
> >
I store it, thank you. But we want to add something before commiting.
Christopher Kings-Lynne wrote:
Are my mails getting through? Did anyone see my mail about the GIN docs?
---(end of broadcast)---
TIP 5: don't forget to increase your free space
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
Christopher Kings-Lynne wrote:
Are my mails getting through? Did anyone see my mail about the GIN docs?
I got it.
Joshua D. Drake
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
=== The Postgre
"Magnus Hagander" <[EMAIL PROTECTED]> wrote:
> > FILE_SHARE_DELETE
>
> I think this is what we want. It passes regression tests on my machine.
> I never managed to reproduce the original problem on this machine, so
> don't know if it solves the problem, but I don't think it makes it worse
> :-)
Are my mails getting through? Did anyone see my mail about the GIN docs?
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Andrew Dunstan wrote:
> Looking at this further, I am wondering if it would not be better to put
> sample .emacs and .vimrc files in the source (in, say, src.tools).
What does people use in .vimrc? Mine has simply this:
: set cinoptions=(0
: set tabstop=4
: set shiftwidth=4
wrapped in a
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
David Fetter wrote:
On Wed, Aug 30, 2006 at 06:28:06PM -0400, Andrew Dunstan wrote:
David Fetter wrote:
thoughts?
If we put them in a place that's visible before you get the source,
we can help people use the settings globally :)
The likely level of our influence on someone who hasn't used th
On Wed, Aug 30, 2006 at 06:28:06PM -0400, Andrew Dunstan wrote:
> David Fetter wrote:
> >>
> >>thoughts?
> >
> >If we put them in a place that's visible before you get the source,
> >we can help people use the settings globally :)
>
> The likely level of our influence on someone who hasn't used th
Hello -hackers,
I see a make check failures on Itanium2 platform with Intel Compiler
with CVS HEAD. A failure is coming for GIN.
The problem is coming at the assertion at ginbulk.c:62
TRAP: FailedAssertion("!(res != 0)", File: "ginbulk.c", Line: 62)
during the index creation from the regr. te
=?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
Andrew Dunstan wrote:
> David Fetter wrote:
> >If we put them in a place that's visible before you get the source, we
> >can help people use the settings globally :)
>
> The likely level of our influence on someone who hasn't used the
> settings and isn't editing our source code is approximately
David Fetter wrote:
Looking at this further, I am wondering if it would not be better to
put sample .emacs and .vimrc files in the source (in, say,
src.tools).
The docs/FAQ would just say that we use BSD style with tab space 4
and refer to the sample files.
thoughts?
If we put them in a
Victor B. Wagner wrote:
> First one is useful if for some reason some ciphers supported by
> OpenSSL is not permitted to use in the particular network, or if
> there is need to use ciphersuites which are not included into default
> ciphersuite list, now compiled into PostgreSQL.
Do you have specif
On Wed, Aug 30, 2006 at 11:06:01AM -0400, Andrew Dunstan wrote:
> Bruce Momjian wrote:
> >Andrew Dunstan wrote:
> >
> >>I will try to draw all this together today or tomorrow. It's not only
> >>the FAQ that should be patched - the docs and the FAQ should agree with
> >>each other.
> >
> >Right.
On Wed, Aug 30, 2006 at 12:12:30 +0300,
Devrim GUNDUZ <[EMAIL PROTECTED]> wrote:
>
> More will be in FC Extras. Please let me know that if you want to see
> any PostgreSQL related software in the repository. I do have time to
> package all related stuff.
Do you think you could have a way to sto
Michael Fuhr wrote:
> In README.pgcrypto, Section 2.3 "Deprecated functions" says that
> digest_exists(), hmac_exists(), and cipher_exists() are planned to
> be removed in PostgreSQL 8.2. Those functions still exist -- should
> they be removed or does that section need updating?
Marko, any commen
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> It looks straightforward to apply our reimplemented pgwin32_open()
>> followed by fdopen(), but since I don't have a Windows build
>> environment I couldn't test the patch. Please take a look at it.
> I think this is what we want. It passes regress
> >> It looks to me like we have implemented Windows'
> FILE_SHARE_DELETE
> >> flag for open() calls but not for fopen(). Isn't this a
> problem?
> >> We do use fopen() for stuff like pgstat.stat.
>
> > That definitely sounds like a problem, there is no reason why the
> > issue shouldn't occur fo
Chris Browne <[EMAIL PROTECTED]> writes:
> If I touch preproc.y and pgc.l, the .c files get regenerated, and all
> is well.
> If I don't, they get left alone, and I see compilation errors.
> It seems to me you need to rebuild the C files and commit them.
No, because those derived files are not i
[EMAIL PROTECTED] (Michael Meskes) writes:
> On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote:
>> >Ah. So this would have caused a bunch of problems in compiling
>> >src/interfaces/ecpg/test/connect/test1.pgc???
>
> Not the compilation errors I would think.
>
>> i'm seeing this error
On 8/30/06, Michael Meskes <[EMAIL PROTECTED]> wrote:
On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote:
> i'm seeing this error when compiling HEAD (updated at ago 29 15:16)
> ...
This looks like you're using an old version of the parser. preproc.y was
changed to handle empty datab
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
Hi,
if you want to use a gui-tool try pgadmin3
http://www.postgresql.org/ftp/pgadmin3/release/v1.4.3/win32/
if you want to access your db from a generic client tool like access
try the pgsqlodbc-driver
official page
http://pgfoundry.org/projects/psqlodbc/
latest snapshots
http://www.geocities.
mario tovilla wrote:
Hi!! I hope you are not too busy.
The thing is that i need to connect my pc which is on windows XP and
the server is on linux with postgres.
The question is?
how do I connect my windows machine to the server with postgres?
What do I have to do?, put it in steps please!!!
> > The code 2 means ERROR_FILE_NOT_FOUND, "The system cannot find
> the
> > file specified." and the code 32 means ERROR_SHARING_VIOLATION,
> "The
> > process cannot access the file because it is being used by
> another process."
>
> The first of those is probably normal operation --- we remove
>
Hi!! I hope you are not too busy.
The thing is that i need to connect my pc which is on windows XP and the
server is on linux with postgres.
The question is?
how do I connect my windows machine to the server with postgres?
What do I have to do?, put it in steps please!!!
thanks you guys are gr
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Looking at this further, I am wondering if it would not be better to put
> sample .emacs and .vimrc files in the source (in, say, src.tools).
Seems reasonable. I was about to say "what if they're just looking at
the docs and don't have a source tree?"
On Tue, Aug 29, 2006 at 03:53:57PM -0700, Joshua D. Drake wrote:
> Hello,
>
> Can we get:
>
> Multiple table indexes (for uniqueness across partitions for example)
Before any of the below happen, I think it'd be good to get a cleaner
way to define partitions; one that didn't involve manually mes
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> It looks to me like we have implemented Windows' FILE_SHARE_DELETE
>> flag for open() calls but not for fopen(). Isn't this a problem?
>> We do use fopen() for stuff like pgstat.stat.
> That definitely sounds like a problem, there is no reason why
On Tue, Aug 29, 2006 at 09:23:53PM -0700, Josh Berkus wrote:
> Peter,
>
> > OK, it seems that while everyone wants autovacuum be more aggressive by
> > default, no one has any good data to support one setting or another. I
> > so I suggest that we just cut scale factor and base threshold in half
Bruce Momjian wrote:
Andrew Dunstan wrote:
I will try to draw all this together today or tomorrow. It's not only
the FAQ that should be patched - the docs and the FAQ should agree with
each other.
Right.
In fact, this info arguably belongs in one place only. Which should it be?
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> I tested HEAD on Windows and saw some Windows-specific logs.
> LOG: Windows fopen("base/16384/pg_internal.init","rb") failed: code 2, errno
> 2
> LOG: Windows fopen("global/pgstat.stat","rb") failed: code 32, errno 13
> The code 2 means ERROR_FILE
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 connect the server.
2. ssl_engine - allows
"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 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
Hello,
Yesterday night, I was approved (sponsored) for Fedora Core packaging
(please note that this is not something financial).
For the beginning, I officially submitted python-psycopg2 to FC6. More
are on the way; like pgpool, Slony-I, pgadmin3-adminpacks, phpPgAdmin,
postgresql_autodoc, pgfoui
On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote:
> >Ah. So this would have caused a bunch of problems in compiling
> >src/interfaces/ecpg/test/connect/test1.pgc???
Not the compilation errors I would think.
> i'm seeing this error when compiling HEAD (updated at ago 29 15:16)
> ...
Is anybody at all from the hackers community going to be at EuroOSCON
this year? (or active users, for that matter) If so, please contact me
off-list. Thanks
//Magnus
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore yo
41 matches
Mail list logo
