Oliver Elphick <[EMAIL PROTECTED]> writes:
> 1. There are regression failures on timestamptz and horology which seem
> to have come about either on input or output of timestamps with
> fractional seconds.
Hmm ... I'm seeing slightly different misbehaviors in the
integer-datetimes and float-dateti
Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
>
2) At what point in the stream does a client_encoding change take effect
-- immediately after the corresponding ParameterStatus message, or at
some other point?
ParameterStatus is sent when the change is made.
Are the strings in the Par
Oliver Jowett <[EMAIL PROTECTED]> writes:
> The encoding of user & database names was my main concern. If they can
> only be 7-bit ASCII in practice, that's easy..
Well, you can *try* using other encodings, but there are enough known
problems that I don't think it will work pleasantly unless clie
On Sun, 30 May 2004, Darko Prenosil wrote:
> Oleg can You take a look at my diffs for tsearch2 (win32 build) ?
> Since the changes are trivial, can You make those changes and commit
> together with schema support?
Where we can get the diff ?
>
> Regards !
>
> - Original Message -
> From
Rod Taylor wrote:
> > > > BEGIN WORK;
> > > > LOCK oldtab;
> > > > CREATE_X TABLE newtab AS SELECT * FROM oldtab;
> > > > DELETE oldtab;
> > > > COMMIT
> > > >
> > > > In this case, you would want the database to abort on a syntax error, right?
> > >
> > >
Heikki Linnakangas wrote:
I'm worried about plan stability if we enable it by default. It could
lead to nasty, hard to reproduce performance problems. Think about this
scenario:
This is my main concern with the approach Tom suggested.
Also keep in mind that at least some application servers have a
Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
1) What encoding is used for strings sent and received during the
startup phase?
The startup packet itself will not get any encoding conversion AFAIR,
so one way to look at it is that the data therein must be in server
encoding. In practi
CVS tip built on Debian unstable, i386, Linux 2.6.5 SMP.
gcc 3.3.3
./configure --with-openssl --with-pam --with-krb5 --with-gnu-ld
--with-python --with-perl --with-tcl --with-pgport=5342
--enable-thread-safety --enable-nls --enable-integer-datetimes
--enable-debug --enable-cassert --enable-depen
Mark,
> It's run #60 and the links are towards the bottom of the page under the
> "Run log data" heading. The results from the power test is
> "power_query.result" and "thuput_qs1.result", etc. for each stream in
> the throughput test.
I'm confused. Were you able to get the original-form query
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Imagine this:
>
> BEGIN WORK;
> LOCK oldtab;
> CREATE_X TABLE newtab AS SELECT * FROM oldtab;
> DELETE oldtab;
> COMMIT
>
> In this case, you would want the database to abort on a syntax error, right?
Certainly not if I
Oleg can You take a look at my diffs for tsearch2 (win32 build) ?
Since the changes are trivial, can You make those changes and commit
together with schema support?
Regards !
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
To: "Oleg Bartunov" <[EMAIL PROTECTED]>
Cc: "Pgsql
Peter Eisentraut wrote:
> Neil Conway wrote:
> > David Helgason <[EMAIL PROTECTED]> writes:
> > > I needed these, so I went and implemented them myself.
> >
> > I didn't see any followup to this: do we want to include this in the
> > main tree, contrib/, or not at all?
>
> getbit sounds a lot like
On Sat, 22 May 2004, Greg Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > I think it's wishful thinking to assume that picking an indexscan is the
> > right thing when we don't know any better.
>
> If we don't know any better then any solution is going to be wishful thinking.
> It's kind
On 12 Feb 2004, Greg Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > > Hmmm ... maybe query_work_mem and maintenance_work_mem, or something
> > > similar?
> >
> > I'll go with these unless someone has another proposal ...
>
> dml_sort_mem and ddl_sort_mem ?
I like those. Are they a
> Hi,
>
> I was toying around with idea of converting all the memory related
> parameters
> in postgresql.conf to kilobytes for simplicity and uniformity.
>
> Attached is a proof of concept patch that converts shared_buffers to
> kilobytes
> using assign_hook.
>
> It compiled all-right but I experi
Shridhar Daithankar <[EMAIL PROTECTED]> writes:
> I was toying around with idea of converting all the memory related
> parameters in postgresql.conf to kilobytes for simplicity and
> uniformity.
Why is that a good idea?
regards, tom lane
---(end of
Oliver Jowett <[EMAIL PROTECTED]> writes:
> 1) What encoding is used for strings sent and received during the
> startup phase?
The startup packet itself will not get any encoding conversion AFAIR,
so one way to look at it is that the data therein must be in server
encoding. In practice, there ar
Shridhar Daithankar wrote:
> Hi,
>
> Platform Slackware linux 9.1/ Linux 2.6.4
>
> I did a make distclean and ./configure --enable-thread-safety. The build
> aborted with following error messages
>
> make[4]: Leaving directory `/home/shridhar/postgresql/pgsql/src/port'
> gcc -O2 -fno-strict-ali
Hi,
Platform Slackware linux 9.1/ Linux 2.6.4
I did a make distclean and ./configure --enable-thread-safety. The build
aborted with following error messages
make[4]: Leaving directory `/home/shridhar/postgresql/pgsql/src/port'
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-de
Hi,
I was toying around with idea of converting all the memory related parameters
in postgresql.conf to kilobytes for simplicity and uniformity.
Attached is a proof of concept patch that converts shared_buffers to kilobytes
using assign_hook.
It compiled all-right but I experienced a strange b
On Sat, 29 May 2004, Alvaro Herrera wrote:
> On Sat, May 29, 2004 at 08:25:27AM -0700, Stephan Szabo wrote:
>
> > BTW: For the deferred trigger stuff, I am guessing you haven't touched
> > that at all in the current patch?
> >
> > I wonder if the following would work assuming that we want deferred
21 matches
Mail list logo
