Hi,
I've run into an odd problem - I have what seems to be a "zombie" tablespace
that PostgreSQL won't let me drop, but nothing inside it is active.
% sudo -H -u postgres psql template1 -c "drop tablespace archive2;"
ERROR: tablespace "archive2" is not empty
% sudo find /media/ssd/archive2/ -ty
On Mon, Oct 19, 2015 at 11:06:59AM +0200, Andres Freund wrote:
> Hi,
>
> On 2015-10-19 10:49:11 +0200, Josip Rodin wrote:
> > % sudo -H -u postgres psql mydb -c "SELECT oid, relname, relkind FROM
> > pg_catalog.pg_class where oid IN (7877054, 7877056);&quo
On Mon, Oct 19, 2015 at 04:39:55AM -0500, Jim Nasby wrote:
> On 10/19/15 4:14 AM, Josip Rodin wrote:
> >On Mon, Oct 19, 2015 at 11:06:59AM +0200, Andres Freund wrote:
> >>Hi,
> >>
> >>On 2015-10-19 10:49:11 +0200, Josip Rodin wrote:
> >>>% sudo
On Mon, Oct 19, 2015 at 11:42:38AM +0200, Andres Freund wrote:
> On 2015-10-19 11:14:33 +0200, Josip Rodin wrote:
> > On Mon, Oct 19, 2015 at 11:06:59AM +0200, Andres Freund wrote:
> > > Hi,
> > >
> > > On 2015-10-19 10:49:11 +0200, Josip Rodin wrote:
> &
On Mon, Oct 19, 2015 at 07:38:32AM -0700, Adrian Klaver wrote:
> What happens if you do?:
>
> select oid, * from pg_tablespace ;
mydb=> select oid, * from pg_tablespace where spcname = 'archive2';
oid | spcname | spcowner | spclocation | spcacl | spcoptions
-+--+---
On Mon, Oct 19, 2015 at 08:23:24AM -0700, Adrian Klaver wrote:
> On 10/19/2015 07:56 AM, Josip Rodin wrote:
> >On Mon, Oct 19, 2015 at 07:38:32AM -0700, Adrian Klaver wrote:
> >>What happens if you do?:
> >>
> >>select oid, * from pg_tablespace ;
> >
On Mon, Oct 19, 2015 at 08:24:10AM -0700, Tom Lane wrote:
> Josip Rodin writes:
> > On Mon, Oct 19, 2015 at 11:42:38AM +0200, Andres Freund wrote:
> >>>> That's the wrong query. The files on disk are relefilenodes not
> >>>> oids. Try WHERE pg_relatio
On Mon, Oct 19, 2015 at 11:15:08AM -0700, Adrian Klaver wrote:
> >Sorry, that's another typo. It's the latter. The symlink is indeed pointing
> >to the 5 GB of leftovers.
>
> This:
>
> % sudo find /media/ssd/archive2/ -type f -ls
> 36962439 393940 -rw--- 1 postgres postgres 403390464 Jun 2
On 19. listopada 2015. 17:46:19 CEST, Adrian Klaver
wrote:
>On 10/19/2015 08:28 AM, Josip Rodin wrote:
>> On Mon, Oct 19, 2015 at 08:23:24AM -0700, Adrian Klaver wrote:
>>> On 10/19/2015 07:56 AM, Josip Rodin wrote:
>>>> On Mon, Oct 19, 2015 at 07:38:32AM -0700, A
On Mon, Oct 19, 2015 at 12:02:17PM -0700, Adrian Klaver wrote:
> >No idea, I inherited this machine. But like Tom said, spclocation being
> >wrong is apparently harmless.
>
> Other then you cannot DROP the tablespace:) This will probably
> needed to be resolved for the reasons that came up in this
On Sun, Oct 25, 2015 at 07:57:48AM -0700, David Blomstrom wrote:
> I can see PostgreSQL is going to have a learning curve - hopefully shorter
> than the years it took me to learn MySQL - but it looks interesting. The
> community seems painfully small compared to MySQL, and there are less
> online r
Hi,
I went looking at why some of our queries using some custom functions were
a bit sluggish.
usercandoonobject(integer, integer, character, integer) does this:
IF (isSuperuser(p_user_id)) THEN
RETURN true;
END IF;
RETURN userCanDoOnObjectCheckGod($1, $2, $3, $4);
issuperus
Thank you both for the helpful explanations.
On Sat, Jul 10, 2010 at 11:48:29AM -0400, Tom Lane wrote:
> Oh, and one more thing: there is no "function cache".
Reading
http://www.postgresql.org/docs/8.3/static/plpgsql-implementation.html
section 38.10.2. "Plan Caching" had put that idea in my hea
On Mon, Jul 12, 2010 at 02:06:43PM +0800, Craig Ringer wrote:
> Meh, personally I'll stick to the good old profiling methods "is it fast
> enough", "\timing", and "explain analyze".
I agree. Some hint could be included in 'explain analyze' output, maybe just
to separate the timings for things th
On Mon, Jul 12, 2010 at 04:38:48PM +0200, Pavel Stehule wrote:
> 2010/7/12 Josip Rodin :
> > On Mon, Jul 12, 2010 at 02:06:43PM +0800, Craig Ringer wrote:
> >> Meh, personally I'll stick to the good old profiling methods "is it fast
> >> enough", "\
On Mon, Jul 12, 2010 at 07:46:30PM +0200, Pavel Stehule wrote:
> 2010/7/12 Josip Rodin :
> > On Mon, Jul 12, 2010 at 04:38:48PM +0200, Pavel Stehule wrote:
> >> 2010/7/12 Josip Rodin :
> >> > On Mon, Jul 12, 2010 at 02:06:43PM +0800, Craig Ringer wrote:
> >&g
Hi,
I've observed an SQL logging problem with FreeRADIUS (2.x) and PostgreSQL
(8.1), on several different installations I occasionally get these errors:
Mon Dec 7 13:19:01 2009 : Error: [ourlittle_sql] Couldn't update SQL
accounting STOP record - ERROR: invalid input syntax for integer: ""
s
On Mon, Dec 07, 2009 at 10:02:39PM +, Adrian Klaver wrote:
> > Mon Dec 7 13:19:01 2009 : Error: [ourlittle_sql] Couldn't update SQL
> > accounting STOP record - ERROR: invalid input syntax for integer: ""
> >
> > accounting_stop_query = "UPDATE ${acct_table2} \
> > SET
> > AcctSessionTim
Hi,
I want to find out whether a user has a select privilege on a particular
database. This is what I see when it does:
# select relacl from pg_class where relname = 'mydbtable';
relacl
--
{
On Tue, Feb 16, 2010 at 12:22:29PM +0100, joy wrote:
> I want to find out whether a user has a select privilege on a particular
> database. This is what I see when it does:
>
> # select relacl from pg_class where relname = 'mydbtable';
> relacl
> -
20 matches
Mail list logo
