Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dIl8t-0007ke-B2 for pgsql-performance@arkaria.postgresql.org; Thu, 08 Jun 2017 00:17:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dIl8s-0005IZ-Ly for pgsql-performance@arkaria.postgresql.org; Thu, 08 Jun 2017 00:17:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dIl77-00025y-Ja; Thu, 08 Jun 2017 00:15:49 +0000 Received: from mail-qt0-x22f.google.com ([2607:f8b0:400d:c0d::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dIl74-0008Kg-Qp; Thu, 08 Jun 2017 00:15:49 +0000 Received: by mail-qt0-x22f.google.com with SMTP id w1so24811259qtg.2; Wed, 07 Jun 2017 17:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fpBJtAO0Wx9ilPPvtak2GnjVHVT4ldu6AV4QSkyYsxA=; b=cvRT7sVs+fmiqr72DgXuwZZShsRRLPVpqVV4W3gN2r499VCY+SfjrViamM0zo4PA43 vu21AUvZSooYdnhXslHNElE37I6L71NGBTGHgROKAu2xWvfOMULJmcUAk6XX4Sjqd2Dp zGHw1LBRfcCq22HIBmua4Z1ENLVlHZJZYdiMs50qoLk8NnDU9mUBk/Wc5x76Z3XCSSU+ szpM9cI5c9b5vSBDnYM668bjAOnPTPKqmrNwv4DXRPlxmnMygsssT0mlneUVrctt93Yn vE1zWGmJFg4KqdIg3+gtPz+J4XEEIjf+vwRXSLWVG3RxyhIU9pjdTui0fsFE3ooAe2F1 uXhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fpBJtAO0Wx9ilPPvtak2GnjVHVT4ldu6AV4QSkyYsxA=; b=cRetQhW/hf8PcwpFi8Snchu+elXRq+UMysK4GyDV6lV4MFdP0dj7g5cdZ0S6JXNfge veaBsUklWbBrReBL74y65Y8PKG13l444dXCveOWxg5XQjVHtUMm8BQsgx2L4Ia5comfc wQCkLp3A4ABV1ZMpozLqrvQxdXF7uFVqU1iT/xzSPDshqgkLrc2n7H2RwcLwWuPRlSEo tmWKh6JwI1Aqc0Sfub7Qw/60ip4C6RYHqeNkr5QM43FNwZbfnPySLJAoNHK9CLFOc1cU WkTkESsa/0Dcsti/LKS1eu5nJuzwW5eEiyyqMRxEDOpGSMQZPaQfLoON/tN67b6pnN37 /Hqg== X-Gm-Message-State: AODbwcCATcHzntfBbw3RT+Ti0Q5F1lyycKIlpFkxzTuMIXbA3HFeZ/A5 hYZLm2kJy7k/tH14+JGZ9fCNLMsg1w== X-Received: by 10.200.52.82 with SMTP id v18mr15707800qtb.214.1496880945053; Wed, 07 Jun 2017 17:15:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.97.35 with HTTP; Wed, 7 Jun 2017 17:15:44 -0700 (PDT) In-Reply-To: References: From: Scott Marlowe Date: Wed, 7 Jun 2017 18:15:44 -0600 Message-ID: Subject: Re: Rollback table data. To: Dinesh Chandra 12108 Cc: "pgsql-performance-owner@postgresql.org" , "pgsql-performance@postgresql.org" Content-Type: text/plain; charset="UTF-8" X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Wed, Jun 7, 2017 at 5:33 AM, Dinesh Chandra 12108 wrote: > Dear Expert, > > > > Is there any way to rollback table data in PostgreSQL? You really need to give us more details. PostgreSQL has the ability, through continuous archiving, to roll back to a previous point in time. This is for the whole database ccluster though and not just one table. BUT you can do it on a whole other machine, get the table data you want, and put it into the production database etc. Got more details? -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance