, per
database, etc.)
--
Mike Nolan.
I don't think the number of tuples is the main problem here, it's the
number of pages a single relation can have. Looking at the numbers of rows
as a direct function of TID size is misleading, because the TID is split
into two fixed parts - page number
give you 2^64 or 1.8 E19 unique
rows over whatever granularity/uniqueness you use (per table, per database,
etc.)
--
Mike Nolan.
Why not take a simpler approach and create a zero length file in
directories that should not be fiddled with by non-experts using a file
name something like DO.NOT.DELETE.THESE.FILES?
No, it won't prevent the incredibly stupid from doing incredibly stupid
things, nothing will.
--
Mike Nolan
= 'postgres'
USER = 'postgres'
PORT = '5432'
ENCODING = 'UTF8'
postgres=#
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
removed them.
FWIW, the documentation for 9.2 still mentions OIDs and the
'default_with_oids' parameter, in what release was it announced they
would be removed and in what release were they removed?
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
to specify
both the directory and the port number?
--
Mike Nolan
the master and slave clocks are synced. We
recommend running NTP. or words to that effect.
What if the two servers are in different time zones?
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
On 5/11/12, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Michael Nolan wrote:
I see one potential difference between your results and mine.
When I rebuild the tablespace, I wind up with the same filename/OID as
before, I'm not sure you do.
Right. That's strange.
Usually OIDs get incremented
On 5/11/12, Michael Nolan htf...@gmail.com wrote:
On 5/11/12, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Michael Nolan wrote:
I see one potential difference between your results and mine.
When I rebuild the tablespace, I wind up with the same filename/OID as
before, I'm not sure you do
, but it probably isn't something most DBAs
would run into very often.
Thanks for figuring it out, Tom.
--
MIke Nolan
code, not a distribution.
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
I see one potential difference between your results and mine.
When I rebuild the tablespace, I wind up with the same filename/OID as
before, I'm not sure you do.
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
to suggest how to repair, because the lost
tablespace only had indexes in it. But that's not exactly a -hackers
issue, more of a question of better backup protocols.
--
Mike Nolan
on this table again, as
expected.
Now, here's the problem I ran into:
The index will be rebuilt in tablespace MYTBLSP, but \d on table MYTABLE
will not show the index as being in that tablespace.
--
Mike Nolan
tables might be needed at the system
level (if not already available) in order to prepare more efficient plans
for some complex read-only queries.
--
Mike Nolan
are they replicated at all?
BTW, should we have an entry in the index for 'temporary tables?
--
Mike Nolan
have negative consequences as well.
Another question:
Does master send WAL to standby before the transaction commit ?
That's another question for the core team, I suspect. A related
question is what happens
if there is a rollback?
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql
On 4/11/12, Kevin Grittner kevin.gritt...@wicourts.gov wrote:
Michael Nolan htf...@gmail.com wrote:
On 4/11/12, 乔志强 qiaozhiqi...@leadcoretech.com wrote:
But when a transaction larger than 1GB...
Then you may need WAL space larger than 1GB as well. For
replication to work, it seems likely
action to take on the master? PANICing
it seems to be a bad idea, but having transactions never complete
because they never hear back from the synchronous slave (for whatever
reason) seems bad too.
--
Mike Nolan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
totals. (SqlPlus
has this, even though it isn't very pretty.)
--
Mike Nolan
On Tue, Sep 13, 2011 at 12:26 PM, Joshua D. Drake j...@commandprompt.comwrote:
On 09/13/2011 10:13 AM, Michael Nolan wrote:
The lists all seem to be focusing on the things that the developers
would like to add to PostgreSQL, what about some things that users or
ISPs might like to have
On Tue, Sep 13, 2011 at 2:55 PM, Joshua D. Drake j...@commandprompt.comwrote:
On 09/13/2011 11:51 AM, Michael Nolan wrote:
The ability to restore a table from a backup file to a different
table
name in the same database and schema.
This can be done but agreed
if that is what schemas are for.
The ability to do cross-database (most likely cross-server as well) queries
would address a lot of real-world problems.
-
Mike Nolan
no...@tssi.com
it to the
output of generate_series();
--
Mike Nolan
no...@tssi.com
to get up to speed would be appreciated, though I
still think it is not just a 'caching' issue.
The question I hesitated to ask in Ottawa was: So, what information would
you like and what would you do with it?
--
Mike Nolan
(and thus actual performance), based on what
has happened recently,
so these statistics would have to be relatively short term and updated
frequently, but without becoming
computational bottlenecks.
The problem is one I'm interested in working on.
--
Mike Nolan
efactoring into smaller functions or
doing a bit of object orientation almost always solves that readability
problem for me.
--
Nolan Cafferky
Software Developer
IT Department
RBS Interactive
[EMAIL PROTECTED]
writer that they did something wrong.
--
Nolan Cafferky
Software Developer
IT Department
RBS Interactive
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: explain analyze is your friend
I received the following note from the original author of dbf2pg:
Date: Tue, 05 Aug 2003 18:43:22 +0400
From: Maarten Boekhold [EMAIL PROTECTED]
Subject: Re: status of dbf2pg
To: [EMAIL PROTECTED]
On 08/03/2003 06:55:01 AM nolan wrote:
What is the status of dbf2pg. There do not appear
([EMAIL PROTECTED]) with no response, but maybe that's an
old address.
--
Mike Nolan
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
for a newbie, I guess. :-)
--
Mike Nolan
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Sorry if I didn't mention it before, but this was on FreeBSD.
--
Mike Nolan
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
More problems with the latest CVS on FreeBSD:
make[3]: Leaving directory `/home/nolan/beta/pgsql/contrib/spi'
/bin/sh ./pg_regress --temp-install --top-builddir=../../.. --schedule=./paralle
l_schedule --multibyte=SQL_ASCII
== removing existing temp installation
no idea
why they are not the default behavior.
Yep, that solved both the make clean and the coredump problems.
Is that piece of information in the developers FAQ anywhere?
--
Mike Nolan
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
This allows functions to read/write operating system files. Is this of
interest to anyone?
Is this something that requires untrusted status, as it would if I
wrote a function in perl to do the same thing?
--
Mike Nolan
---(end of broadcast
it that way ;-). Later in beta, only critical
bugfixes will be accepted, and this one surely ain't very critical.
Now if I can just get CVS working on Redhat 8 and remember how to build
a patch, even a one-liner. :-)
--
Mike Nolan
---(end of broadcast
/utils/adt, but is this a bugfix that can be made during the
pre-beta period for 7.4 or does it need to wait?
--
Mike Nolan
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
earlier
note. As far as I can tell, not capitalizing the first letter after a dash
is the only inconsistency with Oracle's implementation of this function.
If a patch is in order at this time, I will try to produce it, I need to
learn set up CVS and how to do that anyway. :-)
--
Mike Nolan
, a question which is relevant since we're in the
feature freeze for 7.4.
--
Mike Nolan
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
no idea what is the status of that effort right now. You can search the
archives or I hope this kicks a fresh discussion..:-)
I'm game, though I'm also not ready to lead such a project, probably not
even the discussion on it.
--
Mike Nolan
---(end of broadcast
I thought Tablespaces were already implemented. Are they not?
Apparently not.
A group has been formed to work on it, though.
--
Mike Nolan
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
to 'queryout'. To be complete,
would it need to have a command line equivalent, too?
BTW, I figured out how to direct the output to a separate file each time,
I put the following in .psqlrc:
\o |tee `echo psql_${$}.txt`
--
Mike Nolan
---(end of broadcast
,
not tablespace.database.schema.object or database.tablespace.schema.object.
--
Mike Nolan
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
that database. The former is probably
a good thing to require and enforce, the latter is unenforcable but
probably still advisable.
Is this doable within the time frame for the 7.4 feature freeze?
--
Mike Nolan
---(end of broadcast)---
TIP 8
.
--
Mike Nolan
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
completion.
What's the proper way to do this? And what's a good book on writing
portable code?
--
Mike Nolan
---(end of broadcast)---
TIP 8: explain analyze is your friend
places where intermingling to stdout is possible,
especially if readline is used.
Throwing in system('sleep 1'); was the way I resolved the timing
question here, but that may not be portable enough for inclusion into
the code base.
--
Mike Nolan
---(end of broadcast
place:
SYSTEM
USER
TEMP
INDEXES
What about the concepts of a 'read-only' tablespace, or taking tablespaces
offline?
--
Mike Nolan
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
a running record of what I did when, which saves me a LOT
of time if I want to view the results of some query I ran last week.
I can delete or zip up files if I get short on disk space space
--
Mike Nolan
---(end of broadcast)---
TIP 9: the planner
on it yourself if you want it ...
I'm trying to, now I really feel like a rookie! :-)
--
Mike Nolan
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
50 matches
Mail list logo
