What I mean is, do host lookups first in the text file, then if a
pg_hostaccess table (example) exists, check it for host entries. This
alleviates HUP or restart etc. to reload a config file.
David
Bruce Momjian wrote:
>>>
>>>I haven't heard of any more issues with pg_hba.conf so I will mark
When I delete a table that has an OID, the OID does not get deleted
correct? How can I delete the data from the large object?
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEm
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> 1. A non-unique index is already defined over (a, b)
>>
>> - Either add new index or promote existing one to unique?
> Promoting is in my too-hard basket, so I will simply add a new unique index?
> Too bad if it slows them down, as they sh
> >
> >
> >I haven't heard of any more issues with pg_hba.conf so I will mark the
> >item as done. I did cleanup the comments in the file. I have also
> >added a TODO item:
> >
> > * Read pg_hba.conf only on postmaster startup or SIGHUP
> >
>
> If you do this, can you add an access table fo
>
>
>I haven't heard of any more issues with pg_hba.conf so I will mark the
>item as done. I did cleanup the comments in the file. I have also
>added a TODO item:
>
> * Read pg_hba.conf only on postmaster startup or SIGHUP
>
If you do this, can you add an access table for secondary lookup
OK, so just to summarize:
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Tuesday, 10 July 2001 9:39 AM
> To: Hackers
> Subject: [HACKERS] More ADD CONSTRAINT behaviour questions
>
>
> When someone issues this comma
Andrew McMillan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Could we get away with restricting INSERT RETURNING to work only on
>> inserts directly to tables (no ON INSERT DO INSTEAD allowed)? Or is
>> that too much of a kluge?
> Isn't it likely that the person writing the RULE would want t
Andrew McMillan wrote:
>
> mlw wrote:
> >
> > Take these queries:
> >
> > select * from foo as F, (select * from bar where name = 'bla') as B where
> > F.name = B.name
> > union all
> > select * from foo as F, (select * from bar where name = 'bla') as B where
> > F.type = B.type
> >
> > OR
> >
>
Tom Lane wrote:
>
> While this all seems good at first glance, I am wondering just how
> useful it really would be in practice. The problem is: how do you know
> which rows to return in the RETURNS query? If you don't qualify the
> selection then you'll get all the rows in the view, which is su
Hum. Why don't you enable --enable-multibyte and
--enable-unicode-conversion and set client_encoding to UNICODE? That
would do a conversion from/to UTF-8 for Tcl 8.x (x > 9) clients?
--
Tatsuo Ishii
> Eugene Faukin ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the
> Sorry for writting to you but I can´t go further because we are having
> trouble trying to set multibyte in our environment. When I tried to run
> ./configure --enable-multibyte=LATIN2 and after this gmake, I receive lots
> of errors and I don´t know how to proceed. I´m from Brazil and I´m using
Sorry, but I'm not familiar with TH8TISASCII encoding at all. Is there
any documentation for it on the web?
--
Tatsuo Ishii
> Dear Sir,
>
> I have obtained your email address through the PostgreSQL documentation. I
> understood you are the specialist of the localisation on PostgreSQL, and was
>
> I notice from your postings on the PGSQL-hackers archives that you have been
> experimenting with PGSQL and Pgbench. I have not been able to get PGSQL to
> scale on multiple processors. Tom Lane says this is due to the
> implementation of spin-locks. Have you made any fixes or additions to PGS
13 matches
Mail list logo
