On Wed, 28 Jan 2009 23:38:47 +0300 (MSK)
Oleg Bartunov wrote:
> On Wed, 28 Jan 2009, Ivan Sergio Borgonovo wrote:
> > On Tue, 27 Jan 2009 20:45:53 +0300
> > Teodor Sigaev wrote:
> >>> No matter if I drop the trigger that update agg content and the
> >>> fact that I'm just updating d, postgresq
Hi all,
I have written procedure as follows:
-
--procedure begin
Create Procedure sp_getNoOfDays(
ip_startDateIN date,
ip_endDate IN date,
op_noofdays OUT
2009/1/29 sanjeev kumar
> Hi all,
>
> I have written procedure as follows:
> -
> --procedure begin
> Create Procedure sp_getNoOfDays(
> ip_startDateIN date,
> ip_endDate IN date,
>
Phoenix Kiula writes:
> Index Cond: ((user_id)::text = 'superman'::text)
> Filter: (status = 'Y'::bpchar)
> Of course for unregistered users we use user_known = 0, so they are
> excluded from this index. Is this not a useful partial index? I think
> in t
Hi,
I have a database with encoding UTF-8 installed on Windows, and I try to
dump it using pg_dumpall, on the machine on which the database is
installed. I get the following error message:
C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
c:\temp\dbdump.sql
pg_dump: SQL command fa
Hello,
I am using updateable views to have time-based tables (some status is
valid for some time and has to be preserved after updates, inserts and
deletes)
I created DO INSTEAD rules for update, insert and delete, example:
CREATE OR REPLACE RULE formularfeld_update AS
ON UPDATE TO formularfeld
While trying to create a new dictionary for use with PostgreSQL text
search, I get a segfault. My Postgres version is 8.3.5
The dictionary I use is the "Norwegian Bokmål & Nynorsk (Norway) pack
for OOo 2.x" downloaded from
http://wiki.services.openoffice.org/wiki/Dictionaries#Norwegian_.28Norw
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 if you can explain an
Tommy,
I tried your example and didn't find any problem.
My postgresql version is 8.3.3 and I didn't use stopwords, since I don't
have them.
arxiv=# select version();
version
PostgreSQL 8.3.
Could you provide a backtrace? Do you use unchanged norwegian.stop file?
I'm not able to reproduce the bug - postgres just works.
Tommy Gildseth wrote:
While trying to create a new dictionary for use with PostgreSQL text
search, I get a segfault. My Postgres version is 8.3.5
--
Teodor Sigaev
It works on one of my servers:
SELECT version();
version
-
PostgreSQL 8.3.4 on i686-pc-linux-gnu, compiled by GCC cc (GCC) 3.2.3
20030502 (Red
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
DBMS. Be nice to have a "true_
Yes, originaly I used a customized norwegian.stop-file, but I changed
that to the one that comes with PostgreSQL, and got the same error.
How do I make a backtrace?
Teodor Sigaev wrote:
Could you provide a backtrace? Do you use unchanged norwegian.stop file?
I'm not able to reproduce the bug -
I tried without specifying a StopWords-list as well, but same thing happens.
Teodor Sigaev wrote:
Could you provide a backtrace? Do you use unchanged norwegian.stop file?
I'm not able to reproduce the bug - postgres just works.
Tommy Gildseth wrote:
While trying to create a new dictionary for
I have a column, containing the name of the user and there is a need to
organize an indexed search on this column. As far as I understand, I
need to use the full-text search capabilities of postgres.
I would like to attach a dictionary, containing many possible names, and
the short names like:
How do I make a backtrace?
- if you have coredump, just execute gdb /PATH1/postgres gdb /PATH2/core and
type bt. Linux doesn't make core by default, so you allow to do it by ulimit -c
unlimited for postgresql user
- connect to db, and attach gdb to backend process: gdb /PATH1/postgres
BACKEND
to get coredump:
sudo su - postgres
ulimit -c unlimited
pg_ctl restart
Also, Teodor - mind the fact, that his machine is 64, and you've
tested it on 32bits.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
On Thu, 29 Jan 2009, Igor Katson wrote:
I have a column, containing the name of the user and there is a need to
organize an indexed search on this column. As far as I understand, I need to
use the full-text search capabilities of postgres.
I would like to attach a dictionary, containing many
Teodor Sigaev wrote:
How do I make a backtrace?
- if you have coredump, just execute gdb /PATH1/postgres gdb /PATH2/core
and type bt. Linux doesn't make core by default, so you allow to do it
by ulimit -c unlimited for postgresql user
- connect to db, and attach gdb to backend process: gdb /P
if it's
static uint32
makeCompoundFlags(IspellDict *Conf, int affix)
{
uint32 flag = 0;
char *str = Conf->AffixData[affix];
while (str && *str)
{
flag |= Conf->flagval[(unsigned int) *str];
str++;
}
ret
"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 have WIN1252 set as the defa
Hi,
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?
--
Mark
http://www.lambic.co.uk
signature.asc
Description: Digital signature
Oleg Bartunov wrote:
On Thu, 29 Jan 2009, Igor Katson wrote:
I have a column, containing the name of the user and there is a need
to organize an indexed search on this column. As far as I understand,
I need to use the full-text search capabilities of postgres.
I would like to attach a dictio
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/
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
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
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
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 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
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
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
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
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
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, 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
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
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]
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
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
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
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://
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
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 :
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
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
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
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
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
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
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
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
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
-
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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 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, 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
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 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
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
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
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
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
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
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
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
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 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, 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, 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
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 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
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,
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
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
1 - 100 of 123 matches
Mail list logo
