Hi All,
Recently we got into problem of giving permission
to data directory.
(1) Actually we are doing project on PostgreSQL in
group of two. We installed individual copy of PostgreSQL into our group
directory.
(2) When I created data directory and ran "initdb"
it makes me( takes my login
On Sat, 30 Mar 2002, Bruce Momjian wrote:
There is clearly interest from all interfaces. This item has been
requested quite often, usually related to client apps or web apps.
I definitely agree that implementing it in the backend would be the best
plan, if it's feasible. I just can't figure
Hi,
someone asks me about an utility to check any PostgreSQL database
data to be sure that:
1) there is not any page corrupted
(by a memory fault or a damaged disk)
2) re-check any constraint inserted into the database
I really don't know if PostgreSQL itself has any crc check on
its pages.
2) re-check any constraint inserted into the database
There should not be any if it was accepted, however if it's a new
constraint it doesn't get applied to data that already exists. A dump
and restore will ignore these as well (with good reason).
I suppose the easiest way to find if data
It doesn't really say, however, it makes me wonder if it's SGI's KAIO
(http://oss.sgi.com/projects/kaio/) effort which is reported to provide
up to 35% performance improvement for heavily I/O bound applications.
Again, I'm not sure it is SGI's effort that is being talked about here,
nonetheless,
Jessica Perry Hekman [EMAIL PROTECTED] writes:
I definitely agree that implementing it in the backend would be the best
plan, if it's feasible. I just can't figure out how to pass information
back to the driver that the request has been cancelled (and that, in
JDBC's case, a SQLException
We've seen several reports now of 7.2 postmasters failing to start
because of weird networking setups --- if it's impossible to create
a loopback UDP port on 127.0.0.1, 7.2 will exit with
PGSTAT: bind(2): Cannot assign requested address
It occurs to me that a more friendly behavior would
On Sat, Mar 30, 2002 at 09:59:11AM -0600, Greg Copeland wrote:
It doesn't really say, however, it makes me wonder if it's SGI's KAIO
(http://oss.sgi.com/projects/kaio/) effort which is reported to provide
up to 35% performance improvement for heavily I/O bound applications.
I don't think it
On Sat, 30 Mar 2002, Tom Lane wrote:
Why would this be any different from a cancel-signal-instigated abort?
You'd be reporting elog(ERROR) in any case.
If I understand the code correctly, in the case of a cancel signal, the
driver sends the signal and then assumes that the backend has
Jessica Perry Hekman [EMAIL PROTECTED] writes:
If I understand the code correctly, in the case of a cancel signal, the
driver sends the signal and then assumes that the backend has accepted it
and cancelled; the back end does not report back.
Au contraire, it is not assuming anything. It is
On Sat, 30 Mar 2002, Tom Lane wrote:
Au contraire, it is not assuming anything. It is sending off a cancel
request and then waiting to see what happens. Maybe the query will be
canceled, or maybe it will complete normally, or maybe it will fail
because of some error unrelated to the cancel
Cool. Thanks for the information. The only other PAIO effort that I
knew of was the glibc user space effort...
Greg
On Sat, 2002-03-30 at 12:36, Neil Conway wrote:
On Sat, Mar 30, 2002 at 09:59:11AM -0600, Greg Copeland wrote:
It doesn't really say, however, it makes me wonder if it's
Amit Khare writes:
(1) Actually we are doing project on PostgreSQL in group of two. We installed
individual copy of PostgreSQL into our group directory.
(2) When I created data directory and ran initdb it makes me( takes my login name
) as the owner of data directory.
(3) The problem is
Hi all,
In IRC, StuckMojo commented that the following behavior doesn't seem
to be ideal:
nconway= create table my_table (col1 int default 5, col2 int default
10);
CREATE
nconway= create view my_view (col1, col2) as select * from my_table;
CREATE
nconway= create rule insert_rule as on insert to
[EMAIL PROTECTED] (Neil Conway) writes:
In other words, when the insert statement on the view is transformed by
the rule, the default value columns are replaced by explicit NULL
values (which is the default value for the columns of the pseudo-table
created by CREATE VIEW). Is this the correct
On Wed, Mar 27, 2002 at 07:56:15PM -0500, Peter Eisentraut wrote:
Neil Conway writes:
I'm curious; why is this not the right fix? According to the manpage:
-l turns on maximum compatibility with the original
ATT lex implementation. Note that this does not
mean full
Neil Conway writes:
However, it does appear that we can tweak flex for more performance
(usually at the expense of a larger generated parser). In particular, it
looks like we could use -Cf or -CF. Is this a good idea?
Probably. Run some performance tests if you like. It looks like -CFea
BTW. There are good reasons sometimes for having data that violates
current constraints. The top of a tree may have a static record with
a null parent. The NOT NULL constraint added after this entry (via
alter table add constraint) should not affect the static record, so
unless you know
18 matches
Mail list logo
