On Thu, Jan 29, 2009 at 12:41 PM, rhubbell wrote:
> On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
> Jeff Frost wrote:
>
>> On Thu, 29 Jan 2009, rhubbell wrote:
>>
>> > Umm, because md5 doesn't work and trust does work.
>>
>> Generally this is because you haven't yet set a password for the postgres
>>
Martin Gainty wrote:
PROCEDUREs *which compile into Procedure Cache* and have IN/OUT (Mode)
parameters..
Do you mean that as a feature request?
If you intended to say something along the lines of: "I'd like stored
procedures, invoked using 'CALL procname(params)' syntax, as distinct
from SQ
PROCEDUREs *which compile into Procedure Cache* and have IN/OUT (Mode)
parameters..
Martin Gainty
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is
Gregory Stark wrote:
> So, what do people say? Is Postgres perfect in your world or does it do some
> things which rub you the wrong way?
The few things that used to really bug me have gone away between 8.1 and
8.3. The big one is that there are no longer issues with temp tables in
PL/PgSQL funct
Jeff Frost writes:
>> I guess I could pg_dumpall -s | grep "ALTER DATABASE" to grab that stuff.
> That seems silly. Is this the best way to find this data:
> SELECT name, setting FROM pg_settings where source = 'database' ORDER BY
> name;
No, you'd miss anything overridden local
Jeff Frost wrote:
> On Thu, 29 Jan 2009, Tom Lane wrote:
>
>> Jeff Frost writes:
>>> Tom one thing I noticed recently is that pg_dumpall --globals doesn't
>>> seem to pick up when you alter the GUCs at the database level and
>>> neither does pg_dump. How should you dump to grab that per-database
On Thursday 29 January 2009 9:19:15 am rhubbell wrote:
> I'm a new user to PostgreSQL so mine's fresh from doing an install
> recently.
>
>
> In /etc/postgresql/8.3/main/pg_hba.conf
>
> # METHOD can be "trust", "reject", "md5", "crypt", "password", "gss",
> "sspi", # "krb5", "ident", "pam" or "ldap
On Thu, 29 Jan 2009, Tom Lane wrote:
Jeff Frost writes:
Tom one thing I noticed recently is that pg_dumpall --globals doesn't
seem to pick up when you alter the GUCs at the database level and
neither does pg_dump. How should you dump to grab that per-database
stuff?
Regular pg_dumpall will
Jeff Frost writes:
> Tom one thing I noticed recently is that pg_dumpall --globals doesn't
> seem to pick up when you alter the GUCs at the database level and
> neither does pg_dump. How should you dump to grab that per-database
> stuff?
Regular pg_dumpall will catch that.
There's been some pr
On Jan 29, 2009, at 9:43 AM, David Fetter wrote:
On Thu, Jan 29, 2009 at 05:18:19PM +, Gregory Stark wrote:
David Fetter writes:
* No built-in ways to get the information psql gets. "See what
psql is doing" isn't an option when somebody doesn't have psql on
hand.
Uhm, what informatio
On Thu, 29 Jan 2009, Ron Mayer wrote:
- Surely someone wrote a good count(*)-replacement-trigger before.
Now where can I find one? Searching for "count" on pgfoundry
doesn't help me. Searching varlena genralbits find shows me
a simple one, but IIRC is lacking when it comes to concur
Hi all.
I've encountered an SQL problem that I think is beyond my skills...
I've got a table full of records relating to events (phone calls, in
this case) and I need to find the largest number of events (calls)
occurring at the same time.
The table had a start timestamp and a duration field whi
Bill Todd writes:
> I need to join pg_class and pg_constraint to get information about constraints
> on a table. It appears that pg_constraint.conrelid is the foreign key but I do
> not see a relid column in pg_class. What column(s) define the relationship
> between these tables? Thanks.
There'
Bill Todd wrote:
I need to join pg_class and pg_constraint to get information about
constraints on a table. It appears that pg_constraint.conrelid is the
foreign key but I do not see a relid column in pg_class. What
column(s) define the relationship between these tables? Thanks.
Bill
Is the
I need to join pg_class and pg_constraint to get information about
constraints on a table. It appears that pg_constraint.conrelid is the
foreign key but I do not see a relid column in pg_class. What column(s)
define the relationship between these tables? Thanks.
Bill
--
Sent via pgsql-general
On Thu, Jan 29, 2009 at 09:51:42AM -0800, Joshua D. Drake wrote:
> If we are listing pet peeves :)
>
> Up to 8.4, postgresql didn't accurately represent timestamps because
Ah, speaking of timestamps:
GNUmed could nicely use a timestamp with time zone which
preserves the time zone that was used
On Thu, 29 Jan 2009 12:53:20 -0500
Tom Lane wrote:
> Ivan Sergio Borgonovo writes:
> > I succeded to connect to one postgresql server with ssl.
> > Now it's the time of the second... but postgresql clients (pgsql)
> > just look at ~/.postgresql/postgresql.(key|crt)
> > So I can't put in ~/.postg
On Jan 29, 2009, at 12:25 PM, Gregory Stark wrote:
Steve Atkins writes:
6. Where's my CPAN equivalent? Postgresql is extensible, but it's
hard to find
the extension you need, and often harder than it should be to
install.
FWIW our CPAN equivalent is pgfoundry. I don't think we quite h
On Thu, Jan 29, 2009 at 02:22:28PM -0300, Alvaro Herrera wrote:
> > I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> > FOSDEM 2009 this year. I have a pretty good idea what some them are of
> > course,
> > but I would be interested to hear if people have any complaints f
Gregory Stark wrote:
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
* The capitalization that makes everyone (customers, execs, etc) I introduce
it to parse the name as Postgre-SQL.
*
1. pg_dump -d - do i need to explain?
2. psql is not compatible with different (older) version of pg, in terms
of working \x commands
3. lack of optimizer hints
4. lack of covering indexes
5. lack of jobs (like cron, not like something to do to be paid :)
depesz
--
Linkedin: http://www.linked
Steve Atkins writes:
> 6. Where's my CPAN equivalent? Postgresql is extensible, but it's hard to
> find
> the extension you need, and often harder than it should be to install.
FWIW our CPAN equivalent is pgfoundry. I don't think we quite have the
critical mass yet that Perl has to really mak
On Thu, Jan 29, 2009 at 8:10 PM, rhubbell wrote:
>
> Another "Pet Peeve":
>
> Where oh where is pg_config? Oh where oh where can it be?
$PGDIR/bin ?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make change
On Thu, Jan 29, 2009 at 6:53 PM, Tommy Gildseth
wrote:
> Thanks a lot. Exceptional response time :D
> Less than 2.5 hours from problem reported, till a patch was made. Don't
> think there's many projects or commercial products that can compete with
> that ;-)
Oh, wait , it still has to go through
Hi there,
I plan to visit Nepal in april (Annapurna trek), so if there is
an interest I can give a talk about PostgreSQL and discuss
some aspects of full-text search and nepal language.
I heard that PostgreSQL is used in Nepal.
Please, contact me offlist.
Regards,
Oleg
Another "Pet Peeve":
Where oh where is pg_config? Oh where oh where can it be?
On Thu, 29 Jan 2009 13:16:17 +
Gregory Stark wrote:
>
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
On Thursday 29 January 2009, rhubbell wrote:
> On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
>
> Jeff Frost wrote:
> > On Thu, 29 Jan 2009, rhubbell wrote:
> > > Umm, because md5 doesn't work and trust does work.
> >
> > Generally this is because you haven't yet set a password for the
> > postgres use
In response to rhubbell :
> On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
> Jeff Frost wrote:
>
> > On Thu, 29 Jan 2009, rhubbell wrote:
> >
> > > Umm, because md5 doesn't work and trust does work.
> >
> > Generally this is because you haven't yet set a password for the postgres
> > user. You hav
On Thu, Jan 29, 2009 at 02:11:37PM -0500, Tom Lane wrote:
> Mark Styles writes:
> > Thanks, I managed to clear out the offending dependencies. relowner was
> > actually set correctly, but the pg_shdepend records were wrong.
>
> Hmm ... what actually was in the pg_shdepend entries?
I guess I shou
On Thu, Jan 29, 2009 at 09:51:42AM -0800, Joshua D. Drake wrote:
> It should be pg_backup and that is it, with a nice -R flag for restore.
I suppose you think that ssh_add -D is an intuitive interface too? ;-)
A
--
Andrew Sullivan
a...@crankycanuck.ca
--
Sent via pgsql-general mailing list (
On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
Jeff Frost wrote:
> On Thu, 29 Jan 2009, rhubbell wrote:
>
> > Umm, because md5 doesn't work and trust does work.
>
> Generally this is because you haven't yet set a password for the postgres
> user. You have to set a password for at least the postgres
On Thu, 29 Jan 2009, rhubbell wrote:
Umm, because md5 doesn't work and trust does work.
Generally this is because you haven't yet set a password for the postgres
user. You have to set a password for at least the postgres user via ALTER
ROLE while you've still got it set to trust or ident be
On Thursday 29 January 2009, Gregory Stark wrote:
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of
> course, but I would be interested to hear if people have any complaints
> from personal experience
Ok will have a look and get back to you, thanks.
On Thu, 29 Jan 2009 13:39:08 -0500 (EST)
Greg Smith wrote:
> On Thu, 29 Jan 2009, rhubbell wrote:
>
> > So I chose md5 but it will not work, seems like a basic thing. So I am
> > forced to use "trust". These are the kinds of things that wear dow
Umm, because md5 doesn't work and trust does work.
On Thu, 29 Jan 2009 13:16:19 -0500
Bill Moran wrote:
> In response to rhubbell :
> >
> > I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
> >
> > In /etc/postgresql/8.3/main/pg_hba.conf
> >
> > # METHOD can be "trus
The biggest peeve I still have to fight is attached to the old "why aren't
there any optimizer hints?" tree. PostgreSQL forces you to understand a
non-trivial amount of how the query optimizer works before you can get it
to do the right thing once you get beyond a small database, and nobody
li
Mark Styles writes:
> Thanks, I managed to clear out the offending dependencies. relowner was
> actually set correctly, but the pg_shdepend records were wrong.
Hmm ... what actually was in the pg_shdepend entries?
Given the way the code works, this could be explained by a corrupt index
for pg_sh
Mark Styles wrote:
> On Thu, Jan 29, 2009 at 12:29:07PM -0500, Tom Lane wrote:
> > Mark Styles writes:
> > > On Thu, Jan 29, 2009 at 10:46:08AM -0500, Tom Lane wrote:
> > >> I guess the interesting question to me is what happened to the tables
> > >> those toast tables are/were attached to? They s
On Thu, Jan 29, 2009 at 12:29:07PM -0500, Tom Lane wrote:
> Mark Styles writes:
> > On Thu, Jan 29, 2009 at 10:46:08AM -0500, Tom Lane wrote:
> >> I guess the interesting question to me is what happened to the tables
> >> those toast tables are/were attached to? They should have the same
> >> owne
On Thursday 29 January 2009, Terry Fielder
wrote:
> and that ties to:
> 2) If I try to kill 1 postgres pid (e.g. to abort a bad query), the
> whole backend shuts down and rolls back.
> Can we get a way to look at and then kill a specific bad query?
select pg_cancel_backend(pid). Or kill pid from
Teodor Sigaev wrote:
I reproduced the bug with a help of Grzegorz's point for 64-bit box. So,
patch is attached and I'm going to commit it
Thanks a lot. Exceptional response time :D
Less than 2.5 hours from problem reported, till a patch was made. Don't
think there's many projects or commer
On Thu, 2009-01-29 at 13:16 +, Gregory Stark wrote:
> So, what do people say? Is Postgres perfect in your world or does it do some
> things which rub you the wrong way?
The one that has always bothered me is that there's no way to explicitly
set the value that is returned by PQcmdTuples(), i.e
On Thursday 29 January 2009 05:16:17 am Gregory Stark wrote:
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of
> course, but I would be interested to hear if people have any complaints
> from personal
On Thu, 29 Jan 2009, rhubbell wrote:
So I chose md5 but it will not work, seems like a basic thing. So I am
forced to use "trust". These are the kinds of things that wear down
busy people trying use the software. Maybe this is a documentation
enhancement or bug.
I wrote up a first draft of so
On Jan 29, 2009, at 5:16 AM, Gregory Stark wrote:
I'm putting together a talk on "PostgreSQL Pet Peeves" for
discussion at
FOSDEM 2009 this year. I have a pretty good idea what some them are
of course,
but I would be interested to hear if people have any complaints from
personal
experien
Gregory Stark wrote:
Steve Crawford writes:
3. Date handling
Sometimes I've got data with invalid dates and it would be great if it
could replace all the bad ones with, say "-00-00".
Oh dear $DEITY, no.
I think it would be best if we limited ourselves right now to
In response to rhubbell :
>
> I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
>
> In /etc/postgresql/8.3/main/pg_hba.conf
>
> # METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
> # "krb5", "ident", "pam" or "ldap". Note that "password" sen
Tom Lane wrote:
> Gerhard Wiesinger writes:
>
>> Hello Ray,
>> Yes, that's clear. But there was even some stuff which isn't dumped with
>> pg_dumpall (as far as I read).
>>
>
> Perhaps you were reading some extremely obsolete information?
> It used to be that pg_dumpall couldn't dump larg
Steve Crawford writes:
>>> 3. Date handling
>>> Sometimes I've got data with invalid dates and it would be great if it
>>> could replace all the bad ones with, say "-00-00".
>>>
>
> Oh dear $DEITY, no.
I think it would be best if we limited ourselves right now to discussing the
problem
Ivan Sergio Borgonovo writes:
> I succeded to connect to one postgresql server with ssl.
> Now it's the time of the second... but postgresql clients (pgsql)
> just look at ~/.postgresql/postgresql.(key|crt)
> So I can't put in ~/.postgresql/ another [].crt coming from another
> server.
Not an ssl
On Thu, 2009-01-29 at 17:43 +, Richard Huxton wrote:
> David Fetter wrote:
> > * Letter options in psql, pg_dump[all], pg_restore aren't consistent
> > and can easily steer you very wrong. I'm looking at you, -d.
>
> Ah, good one - I keep doing that too. For the record "-d" is usually
> dat
Gerhard Wiesinger writes:
> Hello Ray,
> Yes, that's clear. But there was even some stuff which isn't dumped with
> pg_dumpall (as far as I read).
Perhaps you were reading some extremely obsolete information?
It used to be that pg_dumpall couldn't dump large objects,
but that was a long time bac
Tom Lane wrote:
> Magnus Hagander writes:
>> Tom Lane wrote:
>>> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch,
>>> which seems like an oversight. So you need to fix your locale,
>>> or else use pg_dump directly.)
>
>> IIRC, you can't set the windows console to be UTF8.
>
> Ugh
David Fetter wrote:
> * Letter options in psql, pg_dump[all], pg_restore aren't consistent
> and can easily steer you very wrong. I'm looking at you, -d.
Ah, good one - I keep doing that too. For the record "-d" is usually
database-name, but for pg_dump it's "dump with inserts". Which is a
zill
On Thu, Jan 29, 2009 at 05:18:19PM +, Gregory Stark wrote:
> David Fetter writes:
>
> > * No built-in ways to get the information psql gets. "See what
> > psql is doing" isn't an option when somebody doesn't have psql on
> > hand.
>
> Uhm, what information are you referring to here?
All th
Gregory Stark wrote:
I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
but I would be interested to hear if people have any complaints from personal
experience. What would be most interesting is
Gregory Stark wrote:
> Jason Long writes:
>
>> Richard Huxton wrote:
>>
>>> 1. Case-folding on column-names.
>>> Quoting is a PITA sometimes when you're transferring from a different
>>> DBMS. Be nice to have a "true_case_insensitive=on" flag.
>>>
>> I was just wishing for this the other day.
Magnus Hagander writes:
> Tom Lane wrote:
>> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch,
>> which seems like an oversight. So you need to fix your locale,
>> or else use pg_dump directly.)
> IIRC, you can't set the windows console to be UTF8.
Ugh. That seems to raise the pr
On Thursday 29 January 2009 02:43:18 you wrote:
> On Tue, 2009-01-27 at 12:53 -0500, Gabi Julien wrote:
> > I have merged the last hot standby patch (v9g) to 8.4 devel and I am
> > pleased with the experience. This is promising stuff.
>
> Thanks,
>
> > Perhaps it is a bit too soon to
> > ask questi
3. Date handling
Sometimes I've got data with invalid dates and it would be great if it
could replace all the bad ones with, say "-00-00".
Oh dear $DEITY, no. Part of the ethos of PostgreSQL is that it requires
you to enter valid data. I don't see how auto-replacing one invalid date
Gregory Stark wrote:
Jason Long writes:
Richard Huxton wrote:
1. Case-folding on column-names.
Quoting is a PITA sometimes when you're transferring from a different
DBMS. Be nice to have a "true_case_insensitive=on" flag.
I was just wishing for this the other day.
I
Tom Lane wrote:
> "Moshe Ben-Shoham" writes:
>> C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
>> c:\temp\dbdump.sql
>> pg_dump: SQL command failed
>> pg_dump: Error message from server: ERROR: character 0xd595 of encoding
>> "UTF8" has no equivalent in "WIN1252"
>
> Apparently you h
Mark Styles writes:
> On Thu, Jan 29, 2009 at 10:46:08AM -0500, Tom Lane wrote:
>> I guess the interesting question to me is what happened to the tables
>> those toast tables are/were attached to? They should have the same
>> owners as their parent tables.
> They did have the same owner, I chan
Hi there,
Just noticed this in my webapp logs:
ERROR: FATAL: the database system is in recovery mode
Only one instance, so I'm not too concerned, but why, how often, how
long for, etc.
Am I negelecting to do some important database maintenace?
Could it be related to the backup cron performs
Gregory Stark wrote:
>
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
> but I would be interested to hear if people have any complaints from personal
> experience. What would be most intere
On Thu, Jan 29, 2009 at 05:18:17PM +, Dave Page wrote:
> On Thu, Jan 29, 2009 at 4:57 PM, David Fetter wrote:
>
> > * Neither of them let you set up Slony (or any other replication
> > system) to start with.
^
> pgAdmin does (well, barring installation and setting up s
Jason Long writes:
> Richard Huxton wrote:
>
>> 1. Case-folding on column-names.
>> Quoting is a PITA sometimes when you're transferring from a different
>> DBMS. Be nice to have a "true_case_insensitive=on" flag.
>>
> I was just wishing for this the other day.
I'm kind of wondering what beh
I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
In /etc/postgresql/8.3/main/pg_hba.conf
# METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
# "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
# in clear text; "md5" is
char" issue? Does this affect the old contrib/tsearch2 code?
Checked - No, that was improvement for 8.3 :).
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-general maili
David Fetter writes:
> * No built-in ways to get the information psql gets. "See what psql
> is doing" isn't an option when somebody doesn't have psql on hand.
Uhm, what information are you referring to here?
> * No man pages for the internals.
Is it just that not all of the manual is actu
On Thu, Jan 29, 2009 at 4:57 PM, David Fetter wrote:
> * Neither of them let you set up Slony (or any other replication
> system) to start with.
pgAdmin does (well, barring installation and setting up slon.conf):
http://pgsnake.blogspot.com/2007/09/setting-up-slony-i-with-pgadmin.html
--
Dave
I succeded to connect to one postgresql server with ssl.
Now it's the time of the second... but postgresql clients (pgsql)
just look at ~/.postgresql/postgresql.(key|crt)
So I can't put in ~/.postgresql/ another [].crt coming from another
server.
What should I do to keep stuff separate?
thanks
-
Teodor Sigaev writes:
> Tom Lane wrote:
>> Hmm, seems it's not so much a "64 bit" error as a "signed vs unsigned
>> char" issue?
> Yes, but I don't understand why it worked in 32-bit box.
You were casting to unsigned int. So the offset added to the base
pointer for, say, 255 in the char would
Richard Huxton wrote:
Gregory Stark wrote:
I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
FOSDEM 2009 this year.
Hmm - three "niggles" things leap to mind.
1. Case-folding on column-names.
Quoting is a PITA sometimes when you're transferring from a different
Hello Ray,
Yes, that's clear. But there was even some stuff which isn't dumped with
pg_dumpall (as far as I read).
So it was like to run 2 statements like:
1.) Run pg_dumpall
2.) Run pg_dump additionally ...
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Thu, 29 Jan 2009, Raymond O'Donnell
Gerhard Wiesinger writes:
> Any ideas what additionally has to be dumped to pg_dumpall for a full
> backup?
The configuration files (postgresql.conf, pg_hba.conf, pg_ident.conf),
plus any SSL server keys/certs you might be using --- basically, all
the static text files in the toplevel $PGDATA di
On Thu, Jan 29, 2009 at 01:16:17PM +, Gregory Stark wrote:
>
> I'm putting together a talk on "PostgreSQL Pet Peeves" for
> discussion at FOSDEM 2009 this year. I have a pretty good idea what
> some them are of course, but I would be interested to hear if people
> have any complaints from per
On 29/01/2009 16:31, Gerhard Wiesinger wrote:
> I recently read some Mail on the mailinglist where some parts of
> PostgreSQL were not dumped with pg_dumpall and additionally some pg_dump
> was necessary (it was something like internals, catalog, etc.)
It's the other way around - pg_dump dumps ju
Gregory Stark writes:
> I really think he should just change all the "unsigned int" into "unsigned
> char" and not do the type punning with pointer casts. That's just evil.
Oh, I see. That would work too, but I don't really see that it's a huge
improvement.
What *would* be an improvement IMHO i
Hello!
I recently read some Mail on the mailinglist where some parts of
PostgreSQL were not dumped with pg_dumpall and additionally some pg_dump
was necessary (it was something like internals, catalog, etc.)
Any ideas what additionally has to be dumped to pg_dumpall for a full
backup?
Thnx
Hello Oleg and others.
I also found that reference, but failed to find the corresponding
Chinese dictionary it mentions.
And when I tried to compile nlpbamboo, it fails.
Has one of you tried (and succeeded) to use Tsearch for Chinese?
Thanks for your attention,
Daniel
Oleg Bartunov a écrit :
Tom Lane writes:
> Gregory Stark writes:
>> Maybe I'm missing something but I don't understand how this fixes the
>> problem.
>> s is a "char*" so type punning it to an unsigned char * before dereferencing
>> it is really the same as casting it to unsigned char directly
>
> No, it isn't. If c
In response to Terry Fielder :
>
> 1) if I have multiple pids running queries, say all selects, I have no
> idea which pid is running which query
SELECT * FROM pg_stat_activity;
If the current_query column doesn't have the query in it, then you need
to tweak your postgres.conf settings:
http://
I have 2, closely related:
1) if I have multiple pids running queries, say all selects, I have no
idea which pid is running which query
and that ties to:
2) If I try to kill 1 postgres pid (e.g. to abort a bad query), the
whole backend shuts down and rolls back.
Can we get a way to look at a
Teodor Sigaev writes:
> Tom Lane wrote:
>> Please try to make the commits in the next eight hours, as we have
>> release wraps scheduled for tonight.
> Minor versions or beta of 8.4?
This is just back-branch update releases. 8.4 beta is still a good
ways off :-(
regards
On Thu, Jan 29, 2009 at 4:06 PM, Gregory Stark wrote:
> Gregory Stark writes:
> Ah, I understand how this fixes the problem. You were casting to unsigned
> *int* not unsigned char so it was sign extending first and then overflowing.
:)
> It still seems to me if you put a few "unsigned" in varia
Gregory Stark writes:
> Teodor Sigaev writes:
>
>> I reproduced the bug with a help of Grzegorz's point for 64-bit box. So,
>> patch
>> is attached and I'm going to commit it
> ...
>
>> !Conf->flagval[(unsigned int) *s] = (unsigned char) val;
> ...
>> !Conf->flagval[*(unsigned char*) s]
To be honest, looking through that file, I am quite worried about few
points. I don't know too much about insights of ispell, but I see few
suspicious things in mkSPNode too.
I generally don't want to get involve in reviewing code for stuff I
don't know, But if Teodor (and Oleg) don't mind, I can
On Thu, 2009-01-29 at 19:00 +0300, Teodor Sigaev wrote:
> > Please try to make the commits in the next eight hours, as we have
> > release wraps scheduled for tonight.
>
> Minor versions or beta of 8.4?
Minor versions.
--
Devrim GÜNDÜZ, RHCE
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gun
Gregory Stark writes:
> Maybe I'm missing something but I don't understand how this fixes the problem.
> s is a "char*" so type punning it to an unsigned char * before dereferencing
> it is really the same as casting it to unsigned char directly
No, it isn't. If char is signed then you'll get qu
On Thu, Jan 29, 2009 at 10:46:08AM -0500, Tom Lane wrote:
> Mark Styles writes:
> > I'm trying to drop a role that is no longer being used. However the role
> > has 4 dependencies which are all pg_toast tables. How can I change the
> > owner of those pg_toast tables so I can drop the role?
>
> I
Tom Lane wrote:
Teodor Sigaev writes:
I reproduced the bug with a help of Grzegorz's point for 64-bit box.
Hmm, seems it's not so much a "64 bit" error as a "signed vs unsigned
char" issue?
Yes, but I don't understand why it worked in 32-bit box.
Does this affect the old contrib/tsear
Teodor Sigaev writes:
> I reproduced the bug with a help of Grzegorz's point for 64-bit box. So, patch
> is attached and I'm going to commit it
...
> ! Conf->flagval[(unsigned int) *s] = (unsigned char) val;
...
> ! Conf->flagval[*(unsigned char*) s] = (unsigned char) val;
Maybe I'm mis
Mark Styles writes:
> I'm trying to drop a role that is no longer being used. However the role
> has 4 dependencies which are all pg_toast tables. How can I change the
> owner of those pg_toast tables so I can drop the role?
I guess the interesting question to me is what happened to the tables
th
On Thu, Jan 29, 2009 at 5:16 AM, Gregory Stark wrote:
> So, what do people say? Is Postgres perfect in your world or does it do some
> things which rub you the wrong way?
I would like to see the SQL92 feature for allowing sub-queries in
CHECK constraints, instead of marking this feature as "inte
Teodor Sigaev writes:
> I reproduced the bug with a help of Grzegorz's point for 64-bit box.
Hmm, seems it's not so much a "64 bit" error as a "signed vs unsigned
char" issue? Does this affect the old contrib/tsearch2 code?
Please try to make the commits in the next eight hours, as we have
rele
On Thu, Jan 29, 2009 at 3:32 PM, Teodor Sigaev wrote:
>
>
>> Than I have quite few notes about that function:
>> - affix is not checked on entry, and should be unsigned,
>
> Could be Assert( affix>=0 && affix < Conf->nAffixData )
>
wouldn't that crash pg backend too ?
The structure that this file
On Thu, Jan 29, 2009 at 3:26 PM, Teodor Sigaev wrote:
> I reproduced the bug with a help of Grzegorz's point for 64-bit box. So,
> patch is attached and I'm going to commit it
:)
To be honest, looking through that file, I am quite worried about few
points. I don't know too much about insights of
Than I have quite few notes about that function:
- affix is not checked on entry, and should be unsigned,
Could be Assert( affix>=0 && affix < Conf->nAffixData )
- for sake of safety uint32_t should be used instead of unsigned int,
in the cast
see patch
- there should be some safety limit
I reproduced the bug with a help of Grzegorz's point for 64-bit box. So, patch
is attached and I'm going to commit it
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
*** src/backend/tsearch/
1 - 100 of 123 matches
Mail list logo
