good morning,
I got a bug request for the following unicode character in PostgreSQL
8.1.4: 0xedaeb8
ERROR: invalid byte sequence for encoding "UTF8": 0xedaeb8
This one seemed to work properly in PostgreSQL 8.0.3.
I think the following code in postgreSQL 814 has a bug in it.
File: postgresq
"Rodrigo Hjort" <[EMAIL PROTECTED]> writes:
> > I think more exactly, the planner can't possibly know how to plan an
> > indexscan with a leading '%', because it has nowhere to start.
>
> The fact is that index scan is performed on LIKE expression on a string not
> preceded by '%', except when b
Bruce,
> I am asking again: what is the timetable for merging gborg and
> pgfoundry, and if not, can we set a date to shut down to force the move.
Looking more like mid-June. I didn't have the time for this at the
beginning of May that I thought I would have.
--
--Josh
Josh Berkus
PostgreSQ
I think more exactly, the planner can't possibly know how to plan anindexscan with a leading '%', because it has nowhere to start.
The fact is that index scan is performed on LIKE _expression_ on a string not preceded by '%', except when bound parameter is used.
select * from table where field like
Andreas Pflug <[EMAIL PROTECTED]> writes:
> That's right, but my proposal would implicitely switch on archiving
> while backup is in progress, thus explicitely enabling/disabling
> archiving wouldn't be necessary.
I'm not sure you can expect that to work. The system is not built to
guarantee in
Jim Nasby wrote:
On May 25, 2006, at 11:24 AM, Andreas Pflug wrote:
BTW, I don't actually understand why you want this at all. If you're
not going to keep a continuing series of WAL files, you don't have any
PITR capability. What you're proposing seems like a bulky, unportable,
hard-to-use equ
Marc,
> The thing is, I thought that the scripting work for this was already
> done? Since we're doing CVS->CVS and mailman->mailman, the only major
> scripting effort was required on the gborg-sql -> pgfoundry-sql side of
> things, which I *thought* was already written, just needed alot of
> test
On May 25, 2006, at 11:24 AM, Andreas Pflug wrote:
BTW, I don't actually understand why you want this at all. If you're
not going to keep a continuing series of WAL files, you don't have
any
PITR capability. What you're proposing seems like a bulky,
unportable,
hard-to-use equivalent of pg
Last I heard, JoshB was working on testing it ...
On Thu, 25 May 2006, Joshua D. Drake wrote:
The thing is, I thought that the scripting work for this was already done?
Since we're doing CVS->CVS and mailman->mailman, the only major scripting
effort was required on the gborg-sql -> pgfoundr
Joshua D. Drake wrote:
>> The thing is, I thought that the scripting work for this was already
>> done? Since we're doing CVS->CVS and mailman->mailman, the only major
>> scripting effort was required on the gborg-sql -> pgfoundry-sql side
>> of things, which I *thought* was already written, just n
I'm just experimenting a bit with GIN, and it is occasionally getting
stuck looping in findParents() during WAL replay.
The attached patch seems to fix it. I also had to set ptr->off as
advertised in the comment above the function to avoid triggering
assertions.
GIN isn't fully transparent to me
On Thu, 25 May 2006, Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > I encountered this the other day and set up a build farm client for it.
>
> > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=meerkat&dt=2006-05-25%2018:16:36
>
> That NaN problem has been discussed before,
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> I encountered this the other day and set up a build farm client for it.
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=meerkat&dt=2006-05-25%2018:16:36
That NaN problem has been discussed before, and I believe we concluded
it's a compiler bug.
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Looking at CopySendData, I wonder whether any traction could be gained
>> by trying not to call fwrite() once per character. I'm not sure how
>> much per-call overhead there is in that function. We've done a lot of
>> work trying to o
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
When dumping the table with psql \copy (non-binary), the resulting file
would be 6.6GB of size, taking about 5.5 minutes. Using psql \copy WITH
BINARY (modified psql as posted to -patches), the time was cut down to
21-22 seconds (files
Hello,
I encountered this the other day and set up a build farm client for it.
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=meerkat&dt=2006-05-25%2018:16:36
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Prov
The thing is, I thought that the scripting work for this was already
done? Since we're doing CVS->CVS and mailman->mailman, the only major
scripting effort was required on the gborg-sql -> pgfoundry-sql side of
things, which I *thought* was already written, just needed alot of testing?
I rem
These are two confusing issues.
One is the use of a leading percent sign.
What Tom pointed out was with a bound parameter the planner can't
make any assumptions about indexes.
Leading percent signs can be made to use indexes by creating a
functional index on the column which reverses the o
On Thu, May 25, 2006 at 02:18:10PM -0300, Rodrigo Hjort wrote:
> make a index scan. Otherwise, i.e. using leading '%' on static text or bound
> paremeter, makes the planner always do a sequential scan. Is that the
> scenario?
I think more exactly, the planner can't possibly know how to plan an
ind
On Thu, 25 May 2006, Andrew Dunstan wrote:
Larry Rosenman wrote:
I have Pervasive's blessing to spend paid time working on "community"
projects, and this could be one of them, but every time I try to get more
information about
how things on BOTH gborg and pgfoundry are set up, it takes days, a
Andreas Pflug <[EMAIL PROTECTED]> writes:
> When dumping the table with psql \copy (non-binary), the resulting file
> would be 6.6GB of size, taking about 5.5 minutes. Using psql \copy WITH
> BINARY (modified psql as posted to -patches), the time was cut down to
> 21-22 seconds (filesize 1.4GB a
Larry Rosenman wrote:
I have Pervasive's blessing to spend paid time working on "community"
projects,
and this could be one of them, but every time I try to get more
information about
how things on BOTH gborg and pgfoundry are set up, it takes days, and
lots of the
people have no idea how it
David Fetter wrote:
> On Thu, May 25, 2006 at 10:11:13AM -0700, Joshua D. Drake wrote:
>> Bruce Momjian wrote:
>>> David Fetter wrote:
On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
> I am asking again: what is the timetable for merging gborg and
> pgfoundry, and if no
On Thu, 25 May 2006, Bruce Momjian wrote:
David Fetter wrote:
On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
I am asking again: what is the timetable for merging gborg and
pgfoundry, and if not, can we set a date to shut down to force the
move.
Bruce,
You know that there is
I'm not used to the PG Internals. But let me see if I understood that.The LIKE operator, when applied on a static string and it is not preceded by '%', causes the planner to search for some indexes in the table in order to make a index scan. Otherwise,
i.e. using leading '%' on static text or boun
On Thu, May 25, 2006 at 10:11:13AM -0700, Joshua D. Drake wrote:
> Bruce Momjian wrote:
> >David Fetter wrote:
> >>On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
> >>>I am asking again: what is the timetable for merging gborg and
> >>>pgfoundry, and if not, can we set a date to shu
Bruce Momjian wrote:
David Fetter wrote:
On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
I am asking again: what is the timetable for merging gborg and
pgfoundry, and if not, can we set a date to shut down to force the
move.
Bruce,
You know that there is a tall stack of finick
On Thursday 25 May 2006 10:47, chelsea boot wrote:
> Hi
>
> Can anyone offer advice on this please: Intermittently a postgres process
> appears to crash and the postmaster service needs restarting. The
> following is entered in the log:
>
> 2006-03-15 09:50:03 LOG: server process (PID 348) wa
David Fetter wrote:
> On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
> > I am asking again: what is the timetable for merging gborg and
> > pgfoundry, and if not, can we set a date to shut down to force the
> > move.
>
> Bruce,
>
> You know that there is a tall stack of finicky,
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
This is silly. Why not just turn archiving on and off?
Not quite. I want online backup, but no archiving. Currently, I have to
edit postgresql.conf and SIGHUP to "turn on archiving" configuring a
(hopefully) writa
When preparing to transfer blob data from one database to another (8.0.5
to 8.1.4), I found some interesting numbers that made me suspect that
bytea dumping is more ineffective than expectable.
I have a test dataset of 2000 rows, each row containing a bytea column.
Total disk usage of the tabl
Andreas Pflug <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This is silly. Why not just turn archiving on and off?
> Not quite. I want online backup, but no archiving. Currently, I have to
> edit postgresql.conf and SIGHUP to "turn on archiving" configuring a
> (hopefully) writable directory
I use the \copy command from psql to load data into postgres. I was
fiddling with setting up a database on a HEAD build, and I got the
following new warning
testy=# \copy episodes from 'episodes.data' with delimiter as '\t'
WARNING: nonstandard use of escape in a string literal
LINE 1: COPY epis
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
I propose to introduce a GUC "permanent_archiving" or so, to select
whether wal archiving happens permanently or only when a backup is in
progress (i.e. between pg_start_backup and pg_stop_backup).
This is silly. Why not just turn a
Hi Can anyone offer advice on this please: Intermittently a postgres process appears to crash and the postmaster service needs restarting. The following is entered in the log: 2006-03-15 09:50:03 LOG: server process (PID 348) was terminated by signal 125 2006-03-15 09:50:03 LOG: termina
On Wed, May 24, 2006 at 10:33:53PM -0400, Bruce Momjian wrote:
> I am asking again: what is the timetable for merging gborg and
> pgfoundry, and if not, can we set a date to shut down to force the
> move.
Bruce,
You know that there is a tall stack of finicky, time-consuming work in
order to make
Bruce Momjian writes:
> I am having trouble remembering the name of the new GUC parameter,
> "standard_conforming_strings". I am thinking "standard_strings" is
> clearer, and shorter. I would like to rename this. The parameter will
> be new in 8.2.
The name is already out in places we can't ea
Andreas Joseph Krogh <[EMAIL PROTECTED]> writes:
> What I don't get is why everybody think that because one solution doesn't fit
> all needs on all platforms(or NFS), it shouldn't be implemented on those
> platforms it *does* work on.
(1) Because we're not really interested in supporting multipl
"Massimiliano Poletto" <[EMAIL PROTECTED]> writes:
>> If you call it exactly once, it'll say that exactly once. If you keep
>> calling it "millions of times", it'll keep saying that.
> OK. I wonder, though, why at some point it does in fact return 0.
Probably because you ran out of memory to cr
Andreas Pflug <[EMAIL PROTECTED]> writes:
> I propose to introduce a GUC "permanent_archiving" or so, to select
> whether wal archiving happens permanently or only when a backup is in
> progress (i.e. between pg_start_backup and pg_stop_backup).
This is silly. Why not just turn archiving on and
Bruce Momjian wrote:
> I am having trouble remembering the name of the new GUC parameter,
> "standard_conforming_strings". I am thinking "standard_strings" is
> clearer, and shorter. I would like to rename this. The parameter will
> be new in 8.2.
Nevermind. It was added in 8.1, but as a read-
Alvaro Herrera wrote:
> ipig wrote:
>
> > 2.1) How do I efficiently access information in tables from the backend
> > code?
> > Since heap_open function needs the oid of the relation, how can I get
> > those parameters for heap_open?
> >
> > Suppose that at the beginning, I only know the name of
I am having trouble remembering the name of the new GUC parameter,
"standard_conforming_strings". I am thinking "standard_strings" is
clearer, and shorter. I would like to rename this. The parameter will
be new in 8.2.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDBhttp://www.e
On Thursday 25 May 2006 14:35, korry wrote:
> > That's not workable, unless you want to assume that nothing on the
> > system except Postgres uses SysV semaphores. Otherwise something else
> > could randomly gobble up the semid you want to use. I don't care very
> > much for requiring a distinct
That's not workable, unless you want to assume that nothing on the
system except Postgres uses SysV semaphores. Otherwise something else
could randomly gobble up the semid you want to use. I don't care very
much for requiring a distinct semid to be hand-specified for each
postmaster on a m
ipig wrote:
> 2.1) How do I efficiently access information in tables from the backend code?
> Since heap_open function needs the oid of the relation, how can I get
> those parameters for heap_open?
>
> Suppose that at the beginning, I only know the name of the relation,
> which functions I need t
If you call it exactly once, it'll say that exactly once. If you keep
calling it "millions of times", it'll keep saying that.
OK. I wonder, though, why at some point it does in fact return 0.
Indeed. You forgot to "complete the COPY sequence" before returning
to the PQgetResult loop. As lo
Currently, WAL files will be archived as soon as archive_command is set.
IMHO, this is not desirable if no permanent backup is wanted, but only
scheduled online backup because; it will flood the wal_archive
destination with files that will never be used.
I propose to introduce a GUC "permanen
I was just telling one of the ways to avoid the conflicts. It
generally happens that a newbie adds the cygwin paths to the env
variables and if he forgets to remove those, then, you know better,
which tools he'd be using!!! In such cases, a less experienced person
would just give up.
I reme
Gurjeet Singh said:
>Also, I would recommend uninstalling cygwin before you install
> mingw, because if the mingw doesn't behave properly (gcc won't compile
> files etc...), you could be sure that there definitely is a conflict
> between the cygwin and mingw.
>
>If you don't wish to uninsta
50 matches
Mail list logo
