SQL;
Usage: SELECT nextval(seqname('tablename','colname'));
You might also want to simply keep a table of the sequence names
if you plan on doing this a lot, or make sure you name them in
a consistent and unsurprising manner.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8
the default behavior and always call the
pager, regardless of vertical or horizontal dimensions.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200211070746
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE9ymGFvJuQZxSWSsgRAvKvAJ9qzB76H69DowOYEPdpvwR79j5/6QCg2UQC
there?
FWIW, I use the tags often in some scripts that rely on the output
of 'cvs status -v'. Seeing REL7_3_STABLE at the top of the
Existing Tags list is a bit disconcerting when you know that
it's not true. My scripts assume that the latest release should
always be tagged.
Greg Sabino Mullane
be nice if one or more nameservers were added that
were not in the same subnet, especially because we have so
many mirrors (subdomains) that are scattered all over the globe.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301051008
-BEGIN PGP SIGNATURE-
Comment: http
ads (as previously stated) do not bring in much revenue,
is there a reason to keep them?
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301061347
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+GdDHvJuQZxSWSsgRAhuTAJ9WTsJnBIZfwrgFJ5wPm75OsZ
that.
Sounds like the mirrors could easily absorb more of the traffic from the
main page, especially once we get an easier mirroring system in place.
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301130923
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
are not amenable to putting inside a
view, as they actually compromise multiple SQL calls and some logic in
the C code, but a few could probably be made into views. Could whomever
added that particular TODO item expand on this?
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8
(the community)
provide an alternative to this income, perhaps via direct contributions?
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301131149
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+Iu5+vJuQZxSWSsgRAjkSAJ9Yit8t0GIwigsdf5DZtDVA71vZCgCgz29S
on other things. If there is still a strong interest however, I can easily
help out and share what I have already done.
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301161656
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
, but I still fail to see the pressing need for a backward-compatible
version when the correct one is always shipped with the server.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301221120
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
sense of security. I think this list would be a good place to discuss
how it would be implemented.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302030948
-BEGIN PGP SIGNATURE-
Comment: http://www.gtsm.com/pgp.html
iD8DBQE
, especially the last two. This will
not be that easy of a process, but on the other hand, new versions do not
appear very frequently, and it is important to get this right the first time.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302041207
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can someone point me to an online doc to read through on this?
http://www.desktoplinux.com/articles/AT3341468184.html
http://www.gnupg.org/gph/en/manual.html
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302041356
the ability to revoke it in case of an emergency.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302071451
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+RBJovJuQZxSWSsgRAh3XAJ47eL56YmSKXJCtdAsyYzByMi+m2QCcCNjm
b1tQyp1zLxkpGjhUer6FpZQ=
=Hfpu
-END
of
security. MD5 provides an integrity check only. Any security it
affords (such as storing the MD5 sum elsewhere) is trivial and
should not be considered when using PGP is standard, easy to implement,
and has none of MD5s weaknesses.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8
a unique value that is not already in foo
store this value inside of foo
insert row;
}
commit;
Solution three: use your strategy two, but throw a loop around it and have
it try again (with a new value) if it gets a unique violation.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8
with and without \x
mode.)
I agree with this.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303041444
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+ZQJNvJuQZxSWSsgRArGEAKD4xs+4Ns3syG175T3k80B6MvNJvgCbBkvF
hCkf5SMjLzMJ84uMl1w4tMY=
=a2Uq
-END PGP
information (FILE, LINE, etc.) with different variables. This
should all be doable without a protocol change, as long as everything
is returned as a string in a standard format.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303041516
-BEGIN PGP SIGNATURE-
Comment: http
question - if a protocol change doesn't warrant
a bump to 8.0, what does? :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303040645
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+ZC1LvJuQZxSWSsgRAkJLAKDUE54ZELrPc4ASqEtwUCk7CYJH/ACfZ7nQ
?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303061015
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+Z2bvvJuQZxSWSsgRAhOnAJ9bU3U11TIOuFyPn338Elx9whsO0gCgm/sX
zuiAS4rFB5hYhk0LuxvGMQE=
=9ntO
-END PGP SIGNATURE
item form psql and add a different one to the backend section.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303061020
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+Z2jHvJuQZxSWSsgRAj7IAJ4hLEos9OlE67O02gVrrqxwT9n3AQCeJxto
N2LFyvXPfGY2whPUs5k
(Postgres?)) If it fails, send mail to
webmaster and exit. If it succeeds, run mv $1.temp $1.html. Or use cp
instead of mv and you have a copy of the previous page always preserved.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303111731
-BEGIN PGP SIGNATURE-
Comment: http
of that last missing
piece.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200208021015
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9SpfRvJuQZxSWSsgRAituAJ9t5rFarCQoylBq/467vmALSue9dACg2hxg
GYQWUuPB2uUAxdCismtyOXc=
=eLjg
-END PGP SIGNATURE
of formatting.c
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200209180909
-BEGIN PGP SIGNATURE-
iD8DBQE9iIDvvJuQZxSWSsgRAqRLAJ9gV8oTnMFTsSmQzMdKppNlWW/TvACgvDu2
f0TDVbi//F5jwZn7K9+9wLE=
=TIs7
-END PGP SIGNATURE-
---(end of broadcast
into this; hopefully someone will have started something before then.
If so, count me in as willing to help as well.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200305301423
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
it would certainly be nice if CVS was working first. I am still
getting the following error:
$ cvs update
/projects/cvsroot: no such repository
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200306101553
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
login: authorization failed: server anoncvs.postgresql.org rejected
access to /projects/cvsroot for user anoncvs
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200306102252
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since libpq now keeps track of transaction state, it would be a simple
matter to add a prompt-string % construct to show something that indicates
the state
greg= SELECT 'I am idle';
greg=* SELECT 'I am in a transaction';
greg=! SELECT 'I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- allows us to say that PostgreSQL ships with field-tested
replication in the source tree
We have a winner! I think this one trumps all the rest.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200307160920
-BEGIN PGP
subsequent
requests on the same database handle use that schema.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200307231328
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE/HsXXvJuQZxSWSsgRArfEAJ4+mIE7fTXnvf3JHS2Y3WmSoZwO/QCgxpx0
RuTjTUI3hngy2T9BMqDEXpE
Hi everyone! Did anyone had a chance to use PL/JS for sp development? Im
working on app that uses JS to work with data and was wandering whether PL/JS
can offer full data management functionality like PL/PgSLQ?
Thanks.
Greg.
Cool, will take a look. Thanks!
--- On Tue, 19/10/10, Itagaki Takahiro itagaki.takah...@gmail.com wrote:
From: Itagaki Takahiro itagaki.takah...@gmail.com
Subject: Re: [HACKERS] PL/JS
To: Terri Laurenzo t...@laurenzo.org
Cc: Greg grigo...@yahoo.co.uk, pgsql-hackers@postgresql.org
pgsql-hackers
Hi guys, got across an interesting problem of passing params to a function in
postgre: is it possible to pass a composite parameter to a function without
declaring a type first?
For example:
// declare a function
create function TEST ( object??? )
object???.paramName // using
.
Thanks!
From: Pavel Stehule pavel.steh...@gmail.com
To: Greg grigo...@yahoo.co.uk
Cc: pgsql-hackers@postgresql.org
Sent: Mon, 25 October, 2010 17:46:47
Subject: Re: [HACKERS] Composite Types and Function Parameters
Hello
I am thinking, so it isn't possible
Hi Merlin, I completely forgot about hstore! I'll give it a go. Thanks!
From: Merlin Moncure mmonc...@gmail.com
To: Greg grigo...@yahoo.co.uk
Cc: Pavel Stehule pavel.steh...@gmail.com; pgsql-hackers@postgresql.org
Sent: Mon, 25 October, 2010 23:52:55
Subject
header is for a
different wal stream position.
I think you could actually hack xlogdump to ignore this condition and
keep outputting and you'll see whether the records that follow appear
to be old wal log data. I haven't actually tried this though.
--
greg
--
Sent via pgsql-hackers maili
ng standard SQL, and possibly even find other uses for it.
That kind of abstraction would be more promising for the future than
having yet another C api that is used for precisely one purpose and
whose definition is "provide the data needed for this usage".
--
greg
--
Sent via pgsql-hackers ma
ly need a way to list partitions
without the comments and permissions). At least that doesn't require
the user to learn a new flag and how it interacts with everything
else.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
"Will certainly disappear at some unspecified date" is a lot less
convincing than "will disappear in 2021 in Postgres 14". The specific
year and version number is irrelevant
but picking and naming a specific one makes it a lot easier to follow
through come that date.
--
greg
non-broken coding that requires it. (And if so, there ought to
> be a regression test incorporating that.)
Would it be useful to keep in one of the memory checking assertion builds?
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
On 20 July 2017 at 14:19, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Greg Stark <st...@mit.edu> writes:
>
>> Would it be useful to keep in one of the memory checking assertion builds?
>
> Why? Code that expects to continue accessing a relcache entry's tupdesc
>
ould be to teach one about all the properties and
constraints of our existing data types and operators or for that
matter how easy it would be to figure out what theorems we want proven
to be able to use an index.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
once. Some packages do this by
inventing a foo-shared.o and foo-static.o but that introduces its own
weirdness.
I don't know what the downsides would be of creating a static library
out of objects built with -fPIC. It might just be a small performance
penalty which might be no big deal for libpq. That
On 2 July 2017 at 18:33, Tom Lane <t...@sss.pgh.pa.us> wrote:
> system("cp -a ...") call in favor of something more portable.
If we're ok with using Perl there's File::Copy::Recursive::dircopy()
which does exactly that.
--
greg
--
Sent via pgsql-hackers mailing
hat tuple will never be modified again you could imagine just
replacing the tuple with the LSN of the deletion and letting anyone
who really needs it fetch it from the xlog. That would be a completely
different model from the way Postgres works though. More like a
log-structured storage system.
--
greg
password
hashes or personal data with details censored without giving them
access to the unhashed password or full personal info.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
seful for going in the reverse direction: look up
all the records (or just the last record) that modified a given block.
Instead of having to scan all the wal you would only need to scan the
checkpoint eras that had touched that block.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
w do those two
compare with string sorting in an interesting encoding/locale -- say
/usr/share/dict/polish in pl_PL for example. It's certainly true that
people do sort text as well as numbers. Also, people often sort on
keys of more than one column
--
greg
--
Sent via pgsql-hackers maili
ing 256 * 16
bytes or 2kB for every 8 columns up until the first variable size
column (or I suppose you could even continue in the case where the
variable size column is null).
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
ble.
(I have other advances in pg_stat_statements I would love to see. It
would be so much more helpful if pg_stat_statements also kept a few
examples of query parameters such as the most recent set, the set that
caused the longest execution, maybe the set with the largest of each
metric.)
-
On 1 October 2017 at 16:40, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Greg Stark <st...@mit.edu> writes:
>> Indeed. It's simple enough to export stats to prometheus with queryid
>> as the key. Then even if the query ages out of the database stats you
>> have gr
ting more control over
this heuristic.
For what it's worth I think a good start would be to give people more
visibility into what the tuptoaster heuristic is actually doing to
their data and that will encourage people to give feedback about when
they're surprised and are frustrated by the existi
┼───┤
│ 2 │ 5.08 │
└───┴───┘
(1 row)
Time: 1.997 ms
Yours looks better :)
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
these users out though if there are any. Just
making this change early in a release cycle is the best we can do.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Both the text and csv logging seem to use %d on for logging the server pid:
appendStringInfo(buf, "%d", MyProcPid);
Am I missing something or wouldn't this mean we print pids with large
values as negative numbers? Isn't that strange? Wouldn't we rather use
%u here?
--
greg
--
sure
they would all have the same data. That would also mean that the
timestamps would be in sync and we could probably eliminate the
occurrences of the wrong format appearing in the wrong logs.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to y
ardless of how long a time range they span so if you keep one
changelist for every 10 checkpoints or every 100 checkpoints you could
reduce the storage needs and only lose the time precision.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
We already know this integer overflow checking is non-standard and
compilers keep trying to optimize them out. Our only strategy to
defeat that depends on compiler flags like -fwrapv that vary by
compiler and may or may not be working on less well tested compiler.
So if there's a nice readable
thousands of prefetches (and effective_io_concurrency of 1000 actually
means 7485 prefetches). At some point those i/o are going to start
completing before Postgres even has a chance to start processing the
data.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
vacuum_page_per_delay = 128
vacuum_time_per_delay = 100
Or more likely, something in-between.
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
checkpoint
block until all the writes are completed. You don't actually need to rush them
at all, just know when they're done. That would completely eliminate the i/o
storm without changing the actual pattern of writes at all.
--
greg
---(end of broadcast
Tom Lane [EMAIL PROTECTED] writes:
Greg Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
The main problem with this is knowing which files need to be fsync'd.
Why could the postmaster not just fsync *every* file?
You want to find, open, and fsync() every file
developed could make
for a really nice DML tool.
--
greg
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
it, source code for
SHELF is still available at SourceForge.
ftp://ftp.sourceforge.net/pub/sourceforge/shelf/
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
in a single table versus the dernormalized tables in multiple
tables. The one big exception is any query doing where client_id = ? where
the latter allows the use of a sequential scan instead of an index scan.
--
greg
---(end of broadcast)---
TIP 7: don't
overflowing the fsm.
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
that kept dirty buffers per-fd and couldn't
imagine anyone wanting to do that. It would be fairly easy to check Linux. All
the others out there are fairly closely related to either NetBSD or Solaris.
--
greg
---(end of broadcast)---
TIP 2: you can get
:
Another option is the Debian bug tracking system, which was rewritten recently
and is pretty neat. It's 100% mail driven with web pages to do various
searches and display bugs.
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Manfred Spraul [EMAIL PROTECTED] writes:
Greg Stark wrote:
I'm assuming fsync syncs writes issued by other processes on the same file,
which isn't necessarily true though.
It was already pointed out that we can't rely on that assumption.
So the NetBSD and Sun developers I checked
issue and having postgres mmap the buffers it wants from the
data files. That would avoid the double-buffering entirely including the extra
copy and memory use. But it would be a major change to a lot of core stuff.
And it be tricky to ensure WAL buffers are written before data blocks.
--
greg
they can all share the same value.
That's assuming you only need a transitive relationship, which seems like what
you need.
--
greg
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs
rather than this default.
Wouldn't at least 0750 be safe? That way putting a user in the postgres group
would grant him access to be able to browse around and read the files in
pg_data.
Actually I should think 02750 would be better so that the group is inherited
by subdirectories.
--
greg
as a declaration and therefore initiating a
COMMIT;BEGIN; at the end of every request is perfectly logical, and works fine
in at least Oracle, and probably other databases.
--
greg
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose
if it is a
pathologically hard OS to port to. Just because it was hard doesn't mean it's
useful.
--
greg
---(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
:)
--
greg
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
. Developers will work on what captures
their fancy and the users don't get to vote unless they pay the bills or
contribute the code themselves. :)
--
greg
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
VERY useful. In Oracle they're mainly useful for
low-cardinality attributes like flags on rarely-updated tables. (Actually I
wonder whether locking in postgres would be simpler than locking Oracle
because of the no-update style of MVCC, hmm.)
--
greg
---(end of broadcast
with fits
entirely in memory.
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
and the database can skip
clauses that match the partition clause exactly. Also this is a prime
opportunity for the database to introduce parallel queries because each
partition can be accessed independently.
--
greg
---(end of broadcast
. I'm not sure it's worth the complexity of having to deal with
WHERE xy where x and y are in different locales though.
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
, or effective_cache_size or...
I'm not sure it's as obvious what to put in the HINT though. Ideally these
results would have to be gathered and pumped through linear optimization
algorithms which is a lot more work.
--
greg
---(end of broadcast)---
TIP 9
the data wasn't live for example.
The database is a tool. It's annoying to have a tool that tries to outsmart
the user.
--
greg
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail
for the merge join, the
max is 2x higher than the merge join but the minimum is thousands of times
smaller, then it should consider choosing the nested loop because of the
greater risk of choosing the merge join.
--
greg
---(end of broadcast)---
TIP 5: Have
the real problem is that these numbers are only available
when running with explain on. As shown recently on one of the lists, the
cost of the repeated gettimeofday calls can be substantial. It's not really
feasible to suggest running all queries with that profiling.
--
greg
that count. Nobody else would
be able to insert or delete any records until you either commit or roll back.
That would lead to much lower concurrency, much more contention for locks, and
tons of deadlocks.
--
greg
---(end of broadcast)---
TIP 9
compiled with -fpic because
whenever find one that reaches that threshold they all have to be recompiled.
At least Debian decided long ago to just make everything -fPIC to avoid having
problems later. I don't know what the convention is on other OS's though.
--
greg
by x;
select * from view_2 where x = ?
Actually in this case Postgres does fairly well. It does manage to use the
index though it still uses a GroupAggregate instead of a simple Aggregate
node. The run-time is almost as fast as the straightforward query.
--
greg
also supports global indexes which are indexes that span all the
partitions without having the partition key as the leading columns.
--
greg
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
. Not a README with that message inside.
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Stephan Szabo [EMAIL PROTECTED] writes:
I'd expect copy to be a single command, no matter how many rows were
copied.
It might prevent you from using pg_dump --inserts ?
--
greg
---(end of broadcast)---
TIP 5: Have you checked our extensive
Hannu Krosing [EMAIL PROTECTED] writes:
Greg Stark kirjutas E, 01.12.2003 kell 18:15:
Separate OS partitions is a reasonable use of partitioned tables, but the
biggest advantage is being able to drop and load partitions very quickly, and
without impacting performance at all. loading
is best. Perhaps it should be
buffer_size or something like that?
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
be looking in the code?
--
greg
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
it would be a lot of work and only help in narrow cases though.
--
greg
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
implement gdb functions to help debugging.
But that's a lot of effort for something postgres didn't even need in the
first place.
--
greg
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
to recognize right away or
else you'll spend lots of time puzzling over seemingly good code.
--
greg
---(end of broadcast)---
TIP 8: explain analyze is your friend
]
But what Hannu's saying is that the SQL Standard WITH is precisely syntactic
sugar for subqueries used like above.
It sounds like WITH is to subqueries as let is to lambda
--
greg
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
the GROUP BY or
DISTINCT ON clause but it seems like the user is probably confused if he
really wants a random record and then sort on columns that weren't sorted
previous to the DISTINCT ON.
--
greg
---(end of broadcast)---
TIP 5: Have you checked our
architecture
you're likely to see. But the behaviour is undefined in ANSI 89 C.
As a side-point, personally I find the profusion of casts at every callpoint
to be far uglier, and also more error-prone than the single cast at the
beginning of each call-back.
--
greg
might actually invoke the function
incorrectly. When you call the function you have to call it through a function
pointer with the same type as the prototype the function was defined with to
guarantee all the casts are performed and the proper calling convention is
followed.
--
greg
1 - 100 of 5180 matches
Mail list logo
